Form Save Error on FE DB

[Mollytm]

I have set up an Access 2002 FE/BE database for multiple remote users
mostly using runtime. I have a form that filters a record directly out
of a table, and when the form tries to save, if anyone else has the
form open, it says it can't save and shuts down the database. Would it
help to create a query that pulls the filtered record instead of
filtering for the record in code directly from the table? Is this
locking the table for other users, or could this be a connection
problem with the remote users? It doesn't give a specific error number
or anything, so i am trying to figure out what is going on- does
runtime give error numbers? This is the first time I have worked with
runtime.

 

[Roger Carlson]

I don't really have enough information to answer your questions, but one
thing stands out. You said the error causes the database to shut down. Are
you using a Macro to save the data? One of the liabilites of macros is that
you cannot error trap them and if you have an error, it shuts down the
database in the Run-Time environment. If you are using macros for anything
in your application, you need to convert them to code and add error
trapping.

--
--Roger Carlson
MS Access MVP
Access Database Samples: www.rogersaccesslibrary.com
Want answers to your Access questions in your Email?
Free subscription:
http://peach.ease.lsoft.com/scripts/wa.exe?SUBED1=ACCESS-L

 

[a a r o n . k e m p f]

It's called errorhandling.

I'd put stanrdardized errhandling in every procedure you use. Can't
www.mztools.com vba edition do this-- push errhandling everywhere?)

Public Sub MySub()
on error goto errhandler

Msgbox "Hello World"

cleanexit:
exit sub
errhandler:
msgbox err.number & " - " & err.description
resume next 'or cleanexit or end depending on what you're doing
exit sub