Hi all,

I distributed an Access-frontend to several computers and it works fine.
Only one computer stops the application at a breakpoint that I have been set
once to debug. I cleared the breakpoint before distributing the app. The one
machine still stops there, but the breakpoint is'nt visible (red). When
stopped, F5 runs the app normally. Even compact and repair did not work.
Any suggestions to this??

--
Günter Brandstätter, MCP

Decompile a copy of the database by entering something like this at the
command prompt while Access is not running. It is all one line, and include
the quotes:
"c:\Program Files\Microsoft office\office\msaccess.exe" /decompile
"c:\MyPath\MyDatabase.mdb"

Access keeps 2 copies of the code you an mdb:
- the text version (what you see and edit), and
- the compiles version (what actually executes).
If these 2 copies are out of sync, you see strange errors, including the
failed breakpoints. A decompile tells Access to discard the compiled
version. It then creates the compiled version again from the text, and so
they corruption is gone.

You can avoid this by creating an MDE to give to your users as the front
end. The MDE does not have the text version of the front end and cannot
decompile, so you circumvent that whole issue, avoid that kind of
corruption, and keep nosy users from modifying your forms, reports, and
modules.

--
Allen Browne - Microsoft MVP. Perth, Western Australia.
Tips for Access users - http://allenbrowne.com/tips.html
Reply to group, rather than allenbrowne at mvps dot org.

"G|nter Brandstdtter" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
>
> I distributed an Access-frontend to several computers and it works fine.
> Only one computer stops the application at a breakpoint that I have been
> set once to debug. I cleared the breakpoint before distributing the app.
> The one machine still stops there, but the breakpoint is'nt visible (red).
> When stopped, F5 runs the app normally. Even compact and repair did not
> work.
> Any suggestions to this??