bound forms, corrupt data

I'm working with an inherited Access DB with 5-10 concurrent users.
There is no backend and it sits in a folder on a file server. It has
bound forms (opened with where clause), and access security. A remote
user "crashed the db and corrupted a record". After deleting the
record and repairing and compacting the db, it worked, but I'd rather
avoid this problem. If I split the db to front end\back end (both in
access) and have users download a FE to their pc, should that help the
problem, or would I need to do that and use unbound forms to improve
performance (it is slow)? I'm assuming that an SQL Server BE and
Access FE would be a truly stable solution, right? I'm an experienced
user and write some code, but I don't know much about networks and
performance. Any thoughts would be appreciated.

If I split the db to front end\back end
(both in access) and have users download
a FE to their pc, should that help the
problem,

Yes. The database is less likely to become corrupt. A
FE and BE is the best solution in multi-user
environments.

or would I need to do that and use unbound
forms to improve performance (it is slow)?

No, you don't need to use unbound forms. In fact,
unbound forms will make things much more difficult for
you; you'll need to program the locking records during
edits; you might just as well use bound forms and let
Access do the hard work. I don't think you need worry
about performance.

I'm assuming that an SQL Server BE and
Access FE would be a truly stable solution,
right?

An Access FE running locally and an Access BE on a
server would be stable too.

Any thoughts would be appreciated.

Be careful about securing the FE and BE.
All users will need (access to) the mdw file.

Regards
Geoff




wrote in message
...
I'm working with an inherited Access DB with 5-10
concurrent
users.
There is no backend and it sits in a folder on a file
server.
It has
bound forms (opened with where clause), and access
security. A
remote
user "crashed the db and corrupted a record". After
deleting
the
record and repairing and compacting the db, it
worked, but I'd
rather
avoid this problem. If I split the db to front
end\back end
(both in
access) and have users download a FE to their pc,
should that
help the
problem, or would I need to do that and use unbound
forms to
improve
performance (it is slow)? I'm assuming that an SQL
Server BE
and
Access FE would be a truly stable solution, right?
I'm an
experienced
user and write some code, but I don't know much about
networks
and
performance. Any thoughts would be appreciated.