Problems with runtime 1

[tonyireland]

I sent out a runtime version of my application (Access 2002) to a customer which worked fine when I tested at 'home'. However when the user installed it on his machine (Windows 2000/Access 2000 installed) on double clicking the user received the following message

"Requested type library or wizard is not a VBA project"

also on some of his machines the Access Runtime didn't appear to install at all.

the shortcut that runs the app is like so

"C:\Program Files\Common Files\Microsoft Shared\Access Runtime\Office10\MSACCESS.EXE" /Runtime "C:\Payroll\Payroll Forms 2002.mde"

I used the package and deployment wizard to create my setup

has anyone experienced anything like this?

I've trawled all the usual places and can find nothing.

Thanks

 

[oharab]

Well we can safely assume it's a reference thang!

Do you need all the references you have selected in your original program? If so, then have you included all the relevant OCX's,dll's or tlb's in the package?

Whenever I distribute apps, I usually only have 3 references ticked.

Visual Basic For Applications
Microsoft Access 9.0 Object Library
Microsoft DAO or ADO (depending on the application)

Those are the minimum you will need to run your file. If you can compile your app without adding anything else, then that's all you need.
If you are using automation - word, excel, etc then you may want to add only the required files to the references. Compile it after each one is added, then stop adding when you can compile with no errors.

Now repackage your app, including the files to get your references, and send it to your customer.


hth

Ben ----------------------------------------------
Ben O'Hara

http://www.RobotParade.co.uk

"Where are all the stupid people from...
...And how'd they get so dumb?"
NoFX-The Decline
----------------------------------------------

 

[tonyireland]

Ben
Your suggestion worked well, much appreciated. Given that I'm a Brit my reputation in Ireland has been considerably enhanced!

cheers

Tony