Access Runtime issue

[D.W. Schingenga]

I created an access runtime from a access .mdb database. I installed this on my laptop and it worked fine. However it is intended for my collegue, I installed it on his desktop computer. Problem is it did not work here...!

Both laptop and desktop run Windows XP and I uninstalled the Office package. Problem on the desktop is that it starts up and closes. At some moment after I installed MS Office standard (without access) I started the runtime again and then I get a message "a VBA module should be closed etc." I only can hit OK, and then I get a security message. If I hit continue here the application opens and works fine.

What can cause the above problems? Is there some guide that will lead to a successfull implementation of the runtime solution? I need to install it on another 5 computers as well.

Thanks in advance for you help.

Dirk

 

[vbaInet]

Did you write proper Error Handling in all of your routines and function?

 

[gemma-the-husky]

it may be an operating system/references issue

if you developed in say A2007, and your colleague has A2003, you may get reference issues - as access will not automatically look for an EARLIER MS library than the one you had.

in a run time, that would just generate an immediate rte and crash the programme

 

[D.W. Schingenga]

I did not write de .mdb myself. It is in principal not a complicated Database. De database starts up with a switchboard. I checked the VBA modules, but there is nothing strange with it.

I do not understand why on one system it works fine and on another system it does not, that is why I think it is system related problem.

I did some registry checks and played around with it, but nothing get it to work. If I add aan trusted location in the HKLM (as is on my laptop) to the desktop computer, the application starts and closes without the two messages.

Hope there is somebody who can help out.

Dirk

 

[vbaInet]

I did not write de .mdb myself. It is in principal not a complicated Database. De database starts up with a switchboard. I checked the VBA modules, but there is nothing strange with it.

Why not get the developer to solve the problem if you're not sure about your way around the backend of the db?