Runtime error on ONE pc only, some codes not wokring

[gangel]

Hellloooo !



So i have created an access app (with linked table backend).

It is built with access 2010.

I installed it on to 4 other pcs all with office 2010 installed and ran it with shortcut /runtime.

Weirdly, 2 pcs work 100% fine.. but the ther 2 just come up with Runtime error "close" if you press any button one it has launched.

To be fair, ive never launched a program in my business before and havent got error handlers as I usually just use in normal Dev mode.
So i KNOW i need handlers in there, which is my next step.

But randomly on the off chance is there something that maybe "isnt installed" on the pc that would affect how this runs?

I understand a button maybe having issues, but ALL buttons havent the runtime error is a bit weird, when they all work fine.

Even one of them is just a macro "open form" new record, not even vba code..

Any opinions/advice welcome, thanks!

[ranman256]

I see this too.
1. runtime is unforgiving, if you run in full Access, it continues on but dies in RT.
2. SOME PCs are missing a driver (or version of ) the 1 pc has and the other doesnt. Only Full Access will locate the problem, unless you can narrow down the error and put a msgbox there to trap it.
3 If here is ANY vb code or a call to a control that doesnt exist, NOTHING will work, even opening a form.

try to trap this error using vb ON ERROR GOTO code.

[ItsMe]

There may be a resource that is not available on the PC's that have the exceptions. For instance, an image stored on a server or an image that should be copied to a local drive.

What version of RT did you install on the other PC's? I do not use Macros, personally. However, I have seen threads posted here where macros created using one version of Access do not work on another version of Access.

Not all Macros are backwards compatible and not all Macros are forward compatible. In Access, VBA is much more resilient to the test of time.