Library module updates under W2K 
Author Message
 Library module updates under W2K


I have an App.mde referencing a Lib.mde under Win 2000.
Running under an Access 2000 Runtime references towards a library are lost
when the library is moved.
The solution for this bug, running SR 1, can't be applied to Runtimes (?).
Therefore i made a workaround:

- check the Fullpath property. If not valid anymore then:

- remove the reference from application.references
- add a new reference with the addfromfile method.

First it seemed to work, but a new problem has arisen:

When replacing the library module with an update only, i get the message
....expression/function not known ... is not a VBA project ...
It seems that the application can only reference the library with which it
is compiled. You can't change the App or Lib only?

How can i change App OR Mde versions without having to install both. Suppose
App1, App2, App* are referencing all Lib.
If i install a new version of App1, do i have to recompile and reinstall
App2, App* and Lib also?


Tue, 14 Sep 2004 19:02:04 GMT  
 [ 1 post ] 

 Relevant Pages 

1. CDO update method works W2K but not in NT4

2. Distinguish between XP home/prof, w2k SP level, w2K server/prof

3. Using class modules in a code library

4. Module libraries not found

5. Editing a Library module (A2000)

6. Code Library and Class Modules

7. Useing Class modules in Library mda

8. libraries, modules for vbs

9. Name conflicts with existing module, project or object library

10. Help: Name conflicts with existing module, project or object library

11. Binary compatibility, Public Class, Name conflicts with existing module, project, or object library

12. Name Conflicts with existing module, project or object library


Powered by phpBB® Forum Software