Required Workstation Files for VB EXE

I'm a Newbie in VB and created my first application. After creating the EXE file I tested it on the server (Windows NT 4.0)and everything worked fine. When I attempted to exe the file from a workstation VB requested some DLL's that are not on the workstation. Is there a node installation for workstations ??? What am I doing wrong ???

[MikeS]

When you first ran it on the network you were still probably on your own machine (where VB is installed) and therefore you would have all of the DLLs needed. However to install it on a workstation that doesn't have VB installed you have to go through the "VB Application Setup Wizard".

Good Luck

Hi Mike,
Please forgive my ignorance but could you be a little more specific when you refer to the "VB Application Setup Wizard". Are you saying that I need to install VB on the workstation? I believe this would require me to have a seperate license for each workstation. I installed Mdac_typ.exe & Dcom98.exe and some msvb*.dll that are found in the NT server(where VB is installed, this resulted in being able to exe my program on the workstation but I still get different errors requesting some ActiveX controls as well. And the following error which I believe is related to the workstation not finding the Access DataBase which is also on the Server: "Class not registered. Looking for object with CLSID:{00000010-0000-0010-8000-00AA006D2EA4}"
I wanna be like Mike / Help me out here Please !!!!!!!!

[JHausmann]

How do you launch VB? If you launch it from the start menu, in the Microsoft Visual Basic 5.0 (for example) group (assuming you didn't rename it), you'll find an item called Application Setup Wizard. Try running that.

VB 6.0 has a group Microsft Visual Basic 6.0 tools that has Package and Deployment Wizard. Run that, if appropriate.

Thanks for your help. The only problem I'm having at this time is that the workstations apparently don't see the Access database located on the server. I verified all codes in the VB program that makes reference to the database. All references are pointing to the Access database on the server. The strange thing about all this is that the workstations are looking for the database in "c:\progam files\microsoft visual basic\Cis.mdb" Any ideas ??????

[This message has been edited by JVC (edited 08-13-1999).]

Thanks for all your help...... I was able to get the information needed to resolve the problems from a outside source. Talk to you soon.