missing dll's? 1

[frag]

Ok, this is another thread by frag!

I just finished my current access-project (at least it's in beta-stage). But now i am going really mad... X-)
Here is my problem:

On some machines my project quits with a compiler error:

Can't find project or library.

This happens with the date() and the mid() function! But these functions are standard functions!!

I already tried to copy the VBA files (c:\program files\common files\microsoft shared\vba\) from the machine where my project runs to one of the machines where it doesn't. I haven't to mention that this didn't work!

I am stucked! Get me out... please!!

frag patrick.metz@epost.de

 

[BMeek]

I have had similar issues with error messages. Are you creating your project/program in Access 2000? Are you creating an installation file using the deployment tool? And last of all, did you use the switchboard manager to create the startup form? The errors I had to deal with happened when I created an Access 2000 program and tried to load it on an Access 97 machine. Even though I included Access 2000 Runtime, the program would not run on certain machines.

When creating the deployment file, I manually included the .dll file to make sure the target machine had the file during setup. There are two issues to overcome:
1) Access 2000 Runtime allows you to run the program on an Access 97 machine, but it is in .mde mode. That means you cannot update the references to .dll files on the target machine. If the target machine does not have the .dll file during setup, it cannot install the reference and your program will not run. The file I had to manually include was dao360.dll. During the deployment wizard creating the .cab files for installation, I would add this file to the process.

2) Are you using a switchboard created by the switchboard manager? If so, Access 2000 uses ADO references and Access 97 can only use DAO. Since Access 2000 can run DAO references, I manually recreated my startup form and did not use the switchboard manager. From the Visual Basic Editor, select "Tools" then "References". I removed the reference to MSADO21.TLB and added DAO360.DLL.

I hope this gets you going in the right direction, but the variances between Access 97 and 2000 have caused many error messages when deploying a program to many machines.

Bryan Meek
bmeek@pacbell.net

http://www.handtech.com/meekent

A TC in your corner gives you the personal attention you need to find the right technology solutions for your business.

 

[frag]

Hi BMeek!

I am afraid that won't bring me any further.
I am developing on a machine with Access 97 SR-2 and all the other machines are running the same Access! But my machine is the only one on which my programm runs.
I just created 2 forms with the form-wizzard and put some code in it. I am using standard vba-functions only!

I am really stucked... think of calling Microsoft, but they want to have money...

cya

frag

patrick.metz@epost.de

 

[tedsmith]

Try making a simple prog on one of the other machines and see if it works on yours.
Maybe your or their access97 has corrupted files and needs reinstalling.
If the others are on a network, they may not have installed them properly and just copied them illegally across the network but didnt copy the access.dll type files in the systems directory?
You have to enable the same references on both machines (this is normally done by an instal program like installshield)

 

[frag]

Hi tedsmith!

What do you mean when you say 'references'?
We use fully licensed Access97 version only, even if they are installed (NOT copied) across the network.
How can I figure out if a dll is corrupted or not? I think I wont be able to programm anything on the other machines because they are in use by some very hard working (and stressed) people who won't let me block their system!

-sorry for my bad english-

cya

frag patrick.metz@epost.de

 

[scking]

This is a VERY common problem but fortunately well documented at

http://support.microsoft.com/support/kb/articles/Q160/8/70.asp

If you receive an error such as "Undefined Function," "Function not available in query expressions," or you can't find the object or property you're looking for, then you probably lost some of your library references when you last upgraded. Fortunately, problems with
missing references are easy to resolve. Simply open a module and select References... from the Tool menu. Check the listing in the Available References control. If you find one tagged "Missing," uncheck it. Then, choose Compile and Save All Modules. Doing so should locate and reestablish your missing references.

 

[frag]

Hi scking!

This seams to be very helpful. But I already fixed the problem on a cryptic way... for more infos about that look in the thread: "For anyone who has a little sparetime...".
Could you post your answer to this thread too!?

Thanx.

frag patrick.metz@epost.de