J
Jerry Porter
I have an Access application that references a library mdb. I deliver
this to clients as a runtime application. I've recently migrated to
Access 2002, and have used the Packaging Wizard. I'm having problems
with some installs when I update just the main mdb.
I've read a number of threads and online articles regarding reference
problems. Most don't apply, since my references don't seem to be
broken. I read Michael Kaplan's article at
http://www.trigeminal.com/usenet/usenet026.asp, but I'm not sure it
applies, since calls to VBA functions in the code work fine.
Here are what I think are relevant facts:
1. There's no problem when the app is installed using the Packaging
wizard files. The problem occurs when I try to update just the
application mdb file.
2. Error occurs on call of the Execute method with a SQL statement that
includes Left. The error is "Undefined function 'Left' in expression."
3. Error occurs if library mdb is in app folder, system folder, or
referenced in RefLibPaths key in registry. But not if it is the
original (development) path.
4. If I remove the reference to the libary mdb, and error does not
occur.
5. App _does_ get updated with correct location of the library. I've
included test code to list all the references and locations. Are all
are correct and none is broken, even when the error occurs.
6. If the test pc has Access 2002, refreshing references (by adding and
removing a reference) corrects the problem.
7. I have no OCX's referenced (references are VBA, Access, DAO, ADODB
and library mdb).
Items 3 and 4 imply that my libary mdb is the problem, but I'm confused
why it would be if the app has the correct path in the reference. Is
the library path stored somewhere else? I searched the registry and
found no reference.
Any help will be greatly appreciated. I'd also like to deliver both as
mde files (since user-level security no longer covers modules).
Thanks,
Jerry
this to clients as a runtime application. I've recently migrated to
Access 2002, and have used the Packaging Wizard. I'm having problems
with some installs when I update just the main mdb.
I've read a number of threads and online articles regarding reference
problems. Most don't apply, since my references don't seem to be
broken. I read Michael Kaplan's article at
http://www.trigeminal.com/usenet/usenet026.asp, but I'm not sure it
applies, since calls to VBA functions in the code work fine.
Here are what I think are relevant facts:
1. There's no problem when the app is installed using the Packaging
wizard files. The problem occurs when I try to update just the
application mdb file.
2. Error occurs on call of the Execute method with a SQL statement that
includes Left. The error is "Undefined function 'Left' in expression."
3. Error occurs if library mdb is in app folder, system folder, or
referenced in RefLibPaths key in registry. But not if it is the
original (development) path.
4. If I remove the reference to the libary mdb, and error does not
occur.
5. App _does_ get updated with correct location of the library. I've
included test code to list all the references and locations. Are all
are correct and none is broken, even when the error occurs.
6. If the test pc has Access 2002, refreshing references (by adding and
removing a reference) corrects the problem.
7. I have no OCX's referenced (references are VBA, Access, DAO, ADODB
and library mdb).
Items 3 and 4 imply that my libary mdb is the problem, but I'm confused
why it would be if the app has the correct path in the reference. Is
the library path stored somewhere else? I searched the registry and
found no reference.
Any help will be greatly appreciated. I'd also like to deliver both as
mde files (since user-level security no longer covers modules).
Thanks,
Jerry