It's hard to say whether there's a problem in your app, or the installation of
it. Sounds to me at least possibly it's in the app.

A program or db error can only be diagnosed with Full Access. Otherwise
debugging is disabled and untrapped errors go nowhere. On your development
machine, you can switch between full and runtime mode by whether you include
the "/runtime" switch when you start Access. An mde makes debugging even more
difficult because then not even the code is available.

It can be really difficult to find the cause of an error which occurs only in
runtime and not in full Access. Since we don't know your app, you must be
asking if there's some general well-known problem. Not as far as the
non-specific info you've given, or as far as I can see.

You mention Macros. These tend to be a big no-no in a runtime app (apart from
very simple ones, to start the app, transfer straight to code, whatever). The
reason is for precisely what you state, if you get errors in a macro then it's
curtains really. A Macro, in a Runtime, in an Mde, is great but it's about the
least diagnosable combination I can imagine.

Go back and test your MDB under FULL ACCESS, I can only suggest.
Chris