Hi Again: You would have to define your DataBase: then write a program to populate it with Data: Then a program to access the stored Data:Actually they would be classes designed around the Tables you build for the database and the Window you want to use to look at the data.
What I would do, and have done.I wrote a Logger Class that I could use to print things out easily into a txt file while testing and debugging.
Then:Wrote a program in CSharp to define the DataBase. It may be better to use a script for this but it is the way I started because I knew a little programming but no scripting at the time. Then I wrote a class that generated some test data for the data base and printed it out using the logger.
When that looked good I created a Window to display the data.That's the process. I wrote the first DataBase Definition in CSharp but converted everything to Vb.net and have continued working in it today. As for examples there are plenty of works out there you can find Googling. Problem is you will have to know what to look for. For example, programatically creating a DataBase, Creating a DataBase using Scripts, creating a DataBase using the Sql Server Management Studio Express etc. .. . Read a little and keep asking questions. You will use t-sql in any case so that is something to get a quick overview of. Also, Sql Server Express and DataTypes. If you are new to DataBases look at Create DataBase and Create Table statements to get an overview of a DataBase's structure.
Rick Farmington Mich. USA----- Original Message ----- From: "Andy B" <a_borka@xxxxxxxxxxxxx>
To: <programmingblind@xxxxxxxxxxxxx> Sent: Friday, October 26, 2007 1:04 PM Subject: RE: sql server 2005 express database design How would you do something like this? Any simple examples that I can play with? I will probably be using c# to be the front end... -----Original Message----- From: programmingblind-bounce@xxxxxxxxxxxxx [mailto:programmingblind-bounce@xxxxxxxxxxxxx] On Behalf Of Sina Bahram Sent: Friday, October 26, 2007 12:19 PM To: programmingblind@xxxxxxxxxxxxx Subject: RE: sql server 2005 express database design If you store the files in the database, you actually will get faster performance, all around. Take care, Sina -----Original Message----- From: programmingblind-bounce@xxxxxxxxxxxxx [mailto:programmingblind-bounce@xxxxxxxxxxxxx] On Behalf Of james.homme@xxxxxxxxxxxx Sent: Friday, October 26, 2007 11:58 AM To: programmingblind@xxxxxxxxxxxxx Subject: Re: sql server 2005 express database design Hi andy, In my opinion, you should store the files in the file system and the information about the files in the database. Out of curiosity, what are you going to use as the front-end? Thanks. Jim James D Homme, , Usability Engineering, Highmark Inc., james.homme@xxxxxxxxxxxx, 412-544-1810 "It's more important for me to start to do the right thing than it is to wait until I think I can do it just right." "Andy B" <a_borka@sbcgloba l.net> To Sent by: programmingblind@xxxxxxxxxxxxx programmingblind- cc bounce@freelists. org Subject sql server 2005 express database design 10/26/2007 11:44 AM Please respond to programmingblind@ freelists.org I need to write a program that references, categorizes, indexes and allows searches (including full text searches) on data inserted into the database. Different data formats like Word, rtf, txt, html and other sources would have to be put into the database. Is it easier/better to insert the files themselves (i.e. insert the actual word file) or just the text+formatting of the word file? Any ideas how to do this stuff or where I can find out more? __________ View the list's information and change your settings at //www.freelists.org/list/programmingblind __________ View the list's information and change your settings at //www.freelists.org/list/programmingblind __________ View the list's information and change your settings at //www.freelists.org/list/programmingblind __________View the list's information and change your settings at //www.freelists.org/list/programmingblind