Access back end

L

lewie

I recently split a database. I was just wondering how concerned should
I be about the back end getting corrupt. I was hoping that someone who
has done this for awhile could expound on the likelyhood of the backend
ever becoming corrupt.
Thanks.
Lewie
 
J

Jeff Boyce

Lewie

Scenario 1: a user kicks out the power cord while Access front-end has a
record loaded.
Scenario 2: a user quits Access while it has a record loaded.
Scenario 3: the power goes out while ...
Scenario 4: the network gurus take a switch out of service while ...

Anything that interrupts the normal flow of electrons while Access has a
record loaded (e.g., displaying the record's data in a form) risks
corrupting the database.

Note the "risks corrupting" -- not a foregone conclusion, just a risk.

That said, try Googling Access and corruption for other scenarios. I don't
recall seeing a lot of issues with this.

Regards

Jeff Boyce
Microsoft Office/Access MVP
 
G

Guest

It's not really more likely to become corrupted because it is split.

If it is on the network, there is always a risk of corruption, but if
you have the front end local, at least that part is safe from network
corruption.

(david)
 
L

lewie

does being spllit allow for different versions of access like 2002 and
2003 to access the same db without corrupting?
 
D

Douglas J. Steele

In general, yes. The back-end should be stored in the file format associated
with the oldest version of Access, and each user should have his/her own
copy of the front-end specific to their version of Access. If you're making
changes to the front-end, the changes should be made in the oldest version,
and then converted to the newer version(s), not vice versa.
 
L

lewie

Thanks for all the info.
Does anyone know where there is a good explation of data transfer using
fe/be.
Thanks again.
Lewie
 
J

Jeff Boyce

Lewie

Could you describe a bit more what YOU mean by "data transfer using fe/be"?

Regards

Jeff Boyce
Microsoft Office/Access MVP
 
Top