Import Excel Data - Runtime version

[peg]

I have a client who has the license for the runtime version of Access 2000.

There is a macro setup to initiates the user to find the file (excel) they
want to import. After that they get this message about:

"QuoteCentral can't find the wizard, or there is an incorrect setting in the
windows registry.
Rerun MS Access or MS Office Setup to reinstall the wizards. if the missing
wizard is not a MS Access Wizard, reinstall it using the Add-in Manager."

Has anyone ever run into something like this before? Does the runtime not
have that capability?

 

[Steve Schapel]

Peg,

I do not know the specific answer to your question. However, there is
certainly a range of functionality of the full retail version of Access
that is not available within the runtime. The developer of the
application needs to test the app in the runtime environment, and make
whatever programming provisions are necessary.

 

[peg]

Does anyone know of where I can go to find more info on what the differences
are for RT vs. full version of Access?

 

[George Nicholson]

One main difference between Runtime and Retail versions is that Runtime
doesn't actively support creation of new objects or design modifications to
existing ones. Sometimes it is possible to work around this, however, if
you are importing to a new table, that might be the problem (I can't say
that it is or not, I've never tried). If so, consider importing to an
existing table (even if that table is an empty shell who's sole purpose is
to support data imports).

For an article that lists some of the issues:
http://support.microsoft.com/default.aspx?scid=kb;en-us;208730
ACC2000: Differences Between Retail and Run-Time Microsoft Access

The article implies that hiding design views is the primary thing that
prevents creation/modification of objects. I think that is an
understatement, but it has been a while since I've had to do a Runtime
version, so it may be my memory playing tricks.

I am inclined to think that reliance on "built-in" wizards appearing in the
UI is also a no-no. *Anything* users interact with has to be supplied by
you.