Package Wizard Access 2K3 and Runtime

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

I have recently deployed a couple of databases I created using Access to a
workstation in the office. Unfortunately, neither database has the same
functionality as it did prior to the packaging.

For example:

Database 1 was made using Access 2K3. There are a series of reports, based
on queries, based on a specific table (tblScheduler) which always return an
error in the database running on the workstation. They act the same as they
would if the queries had no data. These reports worked fine before, and
worked on a different computer running the full version of Access 2000.
There may be other problems, but that's the only one I've encountered so far.


Database 2 was made using Access 2K. After using the package wizard to
deploy this database there are many forms I can't open. I get an error about
a license restriction for an ole object, then it crashes to the desktop.
Again, this dataase ran fine on my computer and on a different computer in
the office with Access 2000 installed.

Any suggestions?
 
Apparently all of my troubles were related to macro security; despite
clicking on No to blocking, Yes to opening, and Open anyway to the final
warning. I finally followed some instructions to modify the registry,
needing a change from the painfully frustrating and fruitless endeavor of
"trying to figure it out". Strangely, this aside, which was something I had
been meaning to do for some time, fixed all of my woes...

....well, maybe not ALL of them, but those I reported in the original post
anyway.
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Back
Top