Access 2007 crashes when using subform in datasheet view

[ccampbell107]

Two people are using Access 2007 (database is not split) and both are working
in datasheet view but not on the same set of data. Every third or fourth
time they open a subform, the program kicks one of them out and the data is
lost. Would splitting the database solve the problem? Thank you

 

[M Skabialka]

Splitting databases fixes a whole mess of issues - not the least of which is
less chance of losing data. It's really easy - there's a wizard to help you
through it. If your front end on someone's desktop PC crashes you aren't
going to corrupt the back end with the data anywhere near as easily. And
you can open the same form, though not the same record because of record
locking. Also you can continue to modify your copy of the front end forms
and reports without affecting other people, and give them a final copy once
you have it production ready. Plus, it seems to work faster from my
experience if the FE is on their PC.
Mich

 

[ccampbell107]

:

Thank you Mich. That was my gut feeling, that I should split the database.
I'm working with a split database right now (at another job) and get a little
confused about relinking the tables. When I make a correction on a form on
one computer, do I need to recopy the FE to the other computer or just
relink? Sometimes relinking works and sometimes it doesn't seem to grab the
repaired form or report. I know that if it is a new form, table, query or
report that I need to do the external link.

 

[M Skabialka]

Any changes you make to the design of a form, report, query, etc on a copy
of the front end means that you need to replace everyone else's front end
copy with this new modified copy. Why would you have to relink the tables?
I develop databases in one location and use them at another. At each
location I use the R:\DocData folder (but my development drive mapping is to
a test folder). When I deliver the changed front end it opens the tables in
the R:\DocData without having to relink or anything. The only time you have
to relink is if you add to or delete a table from the back end. If you
modify a table you don't have to relink.

 

[ccampbell107]

Any changes you make to the design of a form, report, query, etc on a copy
of the front end means that you need to replace everyone else's front end
copy with this new modified copy. Why would you have to relink the tables?
I develop databases in one location and use them at another. At each
location I use the R:\DocData folder (but my development drive mapping is to
a test folder). When I deliver the changed front end it opens the tables in
the R:\DocData without having to relink or anything. The only time you have
to relink is if you add to or delete a table from the back end. If you
modify a table you don't have to relink.




Great - that explains it.