ADOX in Access Run-time Environment (Access 2K/SP8

Topic

New Reply

Having purchased the MS Office Premium package for Office 2000, it has the option to generate a deployable version of an mdb or mde file (but not adp, as per the MS Office 2000 Visual Basic Programmer’s Guide). I have been able to use this successfully for a couple of different mde files in the past. However, the current mde file, when installed with the Access Run-time package, provides the following error message in a pop-up window:

“The expression On Click you entered as the event property setting produced the following error: License information for this component not found. You do not have an appropriate license to use this functionality in the design environment.”

The only thing I’m doing in this mde that is different from prior applications is to use ADOX to locate and delete any “linked” tables, prior to issuing dynamic links via a “DoCmd.TransferDatabase acLink” statement. Since it is an mde file, I can’t even get into the source code to set a break point to see if it is this code that is causing the problem, for sure.

If I attempt to run the same code in the mdb version, I get a different, and earlier, pop-up box message:

“The expression On Open you entered as the event property setting produced the following error: Can’t find project or library.”

The above message occurs even before I get the initial form screen displayed, and discards the application upon clicking the “ok” button, so I can’t get to the source via Alt-F11 to set any breakpoints.

The Programmer’s Guide has another pronouncement saying, “The run-time version of Access is a version of Access for which certain features have been disabled, including the ability to create and modify databases.”

While the above does not appear to explicitly prohibit ADOX deletion of linked tables, I’m wondering if someone at MS interpreted “… modify databases” to mean suppression of linked table deletes.

Has anyone else experienced anything of this nature? And is there anyway around it short of installing a full-blown version of Access?

— Jim

Reply | Quote

Replies

This is a bit of a shot in the dark, but it sounds like you may be missing the ADO reference required to use ADOX. Open the VBA editor and check for missing references. Since ADO was in its infancy with Access 2000, I normally use the DAO side of things to deal with TableDefs and linked tables.

Reply | Quote

Wendell,

Well, I went back and removed all ADOX code, using only “DoCmd.DeleteObject acTable strTableName” to remove links. Same result.

However, now that I think on it, the application References include the “Microsoft Excel Object Library”, since the application does data transfers between Access and Excel. I’m now guessing that the problem revolves around the lack of Excel on the install target machine… Duh … Why does it take me so long to see the light!

I’ll have to do some additional testing to verify that guess, but I think that may be it.

Thanks for getting my “thinking-juices” running again.

— Jim

Reply | Quote

Wendell,

Well, I went back and removed all ADOX code, using only “DoCmd.DeleteObject acTable strTableName” to remove links. Same result.

However, now that I think on it, the application References include the “Microsoft Excel Object Library”, since the application does data transfers between Access and Excel. I’m now guessing that the problem revolves around the lack of Excel on the install target machine… Duh … Why does it take me so long to see the light!

I’ll have to do some additional testing to verify that guess, but I think that may be it.

Thanks for getting my “thinking-juices” running again.

— Jim

Reply | Quote

This is a bit of a shot in the dark, but it sounds like you may be missing the ADO reference required to use ADOX. Open the VBA editor and check for missing references. Since ADO was in its infancy with Access 2000, I normally use the DAO side of things to deal with TableDefs and linked tables.

Reply | Quote