What files are needed for Network Distribution of ADO project?

Whew! Finally ready to test my project on our division's Client/Server LAN. We've got 30+ Win98 systems & 10 NT 4.0 SP5 systems. Thanks to Clunietp & others I know I need:

DCOM for the Win98s
MDAC 2.5 for ALL the PCs -since the A2K/VB project uses ADO 2.5.

My question is-what do I need for the actual >VB< program to run on the network. I WAS intending to put the executable, the A2K DB, & the VB dlls on the server & then sprinkle shortcuts on the client PCs pointing to the executable so they could run it. However, I figure that's too easy to work <sg>! Do I need to put something like VBRun60.exe on EVERY freakin client PC to get the VB program to run?? PLEASE tell me that ain't necessary! I'd appreciate any advice-since we're planning to roll this out over the weekend. Thanks!

You would need to install the application with the help of a setup package. The simplest would be to build one through the Package and Deployment Wizard that comes with Visual Studio.

Just copying the dlss and other files on the client machines may not do the trick.

OK, so that means we have to run setup, installing the FULL VB files on EVERY client in the network! If that's true, why would ANY LAN admin EVER agree to accept a VB project?? Considering he'd need to spend the rest of his life installing files just to get the program to run <g>. Somebody PLEASE tell me there's an easier way!

If you have Win98 clients and NT4 SP5 clients, the only file that you must make sure exists is the MSVBVM60.dll. I'm pretty sure your NT clients should have that file, but I believe Win98 ships with the VB5 runtime and not the VB6 runtime......

You'll also have to redistribute the MDAC as well, as 2.5 is a relatively new version (7 MB on EACH system)

So, in short, Sarun is correct. Use the PDW (or your favorite installer). You must run your setup on EACH system to be sure they have the correct files installed & registered


Tom

You mentioned that this was a VB/Access app. Do you plan on having all 40 clients access this database at the same time?

>Do you plan on having all 40 clients access this database at the same time?

Interesting point! Thanks for the advice btw; No I don't envision more than 10-15 new employees MAX taking the test at any 1 time. Do you see that as a problem for A2K handling the hits? We're talking about:
1)each person connecting from his PC & getting a recordset of the questions,
2)then disconnecting & taking the test,
3) then reconnecting the disconnected recordset & saving his answers to the DB.

I'm only worried about #1 if ALL 10-15 people try to hit the DB at ONCE, that could cause a slowdown-right? In your experience, what's the maximum # of users who could connect to the DB without bringing the network to a halt?

Based on y'all's advice, I'm going to TRY to build a PDW that ONLY installs MDAC 2.5 & the MSVBM60.dll on the client PCs. Once that's done, it's just a matter of setting up a shortcut on the client PCs that points to the app + database on the server-right?? Thanks a bunch for the advice & help!

That sounds like it should work just fine, I wouldn't worry about the load on the DB....it doesn't sound like it will be getting too much concurrent activity.

Your setup plan should be fine as well, as long as your EXE doesn't reference any other libraries/controls. Once the dependancies are installed, a shortcut to a EXE that is stored on a network share should be fine.





Tom

Thanks Tom! We postponed the setup due to unforseen circumstances, which has given me more time to work this out. I REALLY appreciate the help you've given.

No problem

I hope you don't mind, but I have taken the liberty of transferring $2,493 in consultancy fees from your bank account to mine :D (just kidding)

As long as it's billed to my company-no problemo!<eg> Seriously, I wish there were some online pub/bar that I could buy the people here a round of drinks for all their help! Now it's on to the joys of error trapping all the functions/subroutines, and then testing the whole shebang on the LAN. I HOPE not to have too many questions about that stuff-but, ya never know! Thanks again for all your help!