Mischamel Posted December 10, 2003 Posted December 10, 2003 Hi, I created a on Datasets and MS Jet 4.0(Access 2002) basing .exe on my workstation. But it shall also be used on other workstations. The Access2002 Db is on a Netfolder, as well as the .exe. So I put the .NET Framework on the other machine and released the .exe and the belonging .dlls. After all this, the programm starts and most functions work properly, except the most important : The application throws an errmsg like this: 'Couldn´t start DB-Server' @ the following line : Dim oAccess As New Access.Application() I guess the system wants the runtime library of Access ?? But I don´t have it or are there any other possibilities than the runtime lib. P.S. The other workstations don´t have Access intalled. Some good ideas out there ?? Quote Sometimes you´ve got to make a silent Takedown .
techmanbd Posted December 10, 2003 Posted December 10, 2003 From answers I have had before about a similar question, YOu don't need access on your workstations, but MDAC 2.7 or higher YOu can download it from here. http://msdn.microsoft.com/library/default.asp?url=/downloads/list/dataaccess.asp Quote Live as if you were to die tomorrow. Learn as if you were to live forever. Gandhi
Moderators Robby Posted December 10, 2003 Moderators Posted December 10, 2003 When you create an instance of 'Access.Application', you DO need Access installed on each machine. Why are you creating an 'Access.Application' object, are you running macros, forms or reports in Access? Quote Visit...Bassic Software
Mischamel Posted December 11, 2003 Author Posted December 11, 2003 Reports and Makros are executed or called . The errmsg is caused, before amakro is being executed. The DB is on a netfolder and the .exe too. Isn´t there another (cheaper) possibility to let this applic. run other machines, than installing Access on all machines ??? Quote Sometimes you´ve got to make a silent Takedown .
Moderators Robby Posted December 11, 2003 Moderators Posted December 11, 2003 Nope, no cheaper solution. The error comes as soon as an istance is created of the Access object. Quote Visit...Bassic Software
Moderators Robby Posted December 11, 2003 Moderators Posted December 11, 2003 techmanbd, I don't think you understand, he is calling reports in Access this has nothing to do with connection to a database. [edit]techmanbd, I guess you deleted your post [/edit] Quote Visit...Bassic Software
Mischamel Posted December 11, 2003 Author Posted December 11, 2003 But why do I include a reference to Access.dll, reference to it only if Access 2002 is installed, obviously. I see. But for other revolutionary tips, that might bypass an AccessInstallation 8-) I would be very apreciated, as you might suppose. Thanks so far ... You did a good Job Quote Sometimes you´ve got to make a silent Takedown .
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.