atmosphere1212 Posted September 15, 2004 Posted September 15, 2004 In general here is the situation -Small program distributed clients, that will be used locally on their computers -Includes databases that will have 1000-3000 entries on average -Want database functionallity: joins, queries, updates, ect -Assume windows XP/NT. Least additional software requriement for users possible -Developed using visual studio .net 2003 What type of db/data storage do you suggest? In your explanation could you please explain what additional software I would need/Users would need. Please elaborate on your answers as I am very new to this. Thank you so much Quote
*Experts* Nerseus Posted September 15, 2004 *Experts* Posted September 15, 2004 Assuming you don't want multiple machines to access the same database, I'd go with Access simply because it's easiest to setup and install on a user's machine: they'll only need the MDA components (MDAC) and the database file you provide. Access can handle multiple users at once, but it's a lot easier if you don't have to worry about. -ner Quote "I want to stand as close to the edge as I can without going over. Out on the edge you see all the kinds of things you can't see from the center." - Kurt Vonnegut
atmosphere1212 Posted September 15, 2004 Author Posted September 15, 2004 They'll only need the MDA components (MDAC) and the database file you provide. Are these MDAC components large? Can I include them in my installation file or do they have to be installed via a microsoft cd? Are they free to share? By the way, thanks for the help Quote
bri189a Posted September 15, 2004 Posted September 15, 2004 Are these MDAC components large? Can I include them in my installation file or do they have to be installed via a microsoft cd? Are they free to share? By the way, thanks for the help If your program using any kind of Database Access, the client machine will need MDAC 2.7 or higher on it anyway, so you should look into having it ready, although if they're using Office with the latest SP (3) they should be good to go. It's not too large and will fit on your install CD and your setup program should check and install it if needed. It's freely distributable from Microsoft. Quote
atmosphere1212 Posted September 15, 2004 Author Posted September 15, 2004 If your program using any kind of Database Access' date=' the client machine will need MDAC 2.7 or higher on it anyway, so you should look into having it ready, although if they're using Office with the latest SP (3) they should be good to go. It's not too large and will fit on your install CD and your setup program should check and install it if needed. It's freely distributable from Microsoft.[/quote'] Thanks for all the help. One more question. Im developing with Microsoft Visual C++ for visual studio .net 2003 (although i dont have access, Infact i dont have office at all). Do I already have these MDAC components installed with .net 2003, or do i have to obtain a copy of access? Quote
*Experts* Nerseus Posted September 15, 2004 *Experts* Posted September 15, 2004 I can't remember the rules for distributing an Access database. You might only need to own a copy of Access (or Office, if it includes Access), or there might be other licensing restrictions. Microsoft has a free 800 number to call about licensing questions. For distributing MDAC... it used to automatically include that with a VB6 installation (the old Package and Deployment Wizard). I would guess that Visual Studio for .NET would also automatically include MDAC if it's needed. If not, simply search at microsoft.com for mdac and you'll get lots of download links. -ner Quote "I want to stand as close to the edge as I can without going over. Out on the edge you see all the kinds of things you can't see from the center." - Kurt Vonnegut
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.