 | |
Unrecognised database format
comp.database.ms-access comp.database.ms-access
 |
| | Thread Tools | Display Modes |
#1
 
| |||
| |||
|
Unrecognised database format -
08-07-2005
, 06:01 AM
#2
| |||
| |||
|
|
I wrote a database appllication that was initially used in the office by me and one person Now four of us use (maybe maximum of 3 at once) it but sometimes I get the message Unrecognised database format Which means the database has crashed ie when closed it cannot be reopened (it still shows the ldb file as active) We use office 2000 and Access 2000 I have a utility program which will fix it again but it is still a nuisance Anyone come across this problem |
#3
| |||
| |||
|
|
You need to "split" your database so that everyone has his/her own copy of the front end .... See these articles for more info about splitting a database: http://www.granite.ab.ca/access/splitapp/index.htm http://www.allenbrowne.com/ser-01.html |
#4
| |||
| |||
|
|
You need to "split" your database so that everyone has his/her own copy of the front end .... See these articles for more info about splitting a database: http://www.granite.ab.ca/access/splitapp/index.htm http://www.allenbrowne.com/ser-01.html |
#5
| |||
| |||
|
|
Thanks Ken I'm trying to digest that I have now split the database but it runs real slow as in opening and opening forms Will keep reading the link stuff On Sun, 7 Aug 2005 15:56:58 -0400, "Ken Snell" kthsneisllis9 (AT) ncoomcastt (DOT) renaetl> wrote: You need to "split" your database so that everyone has his/her own copy of the front end .... See these articles for more info about splitting a database: http://www.granite.ab.ca/access/splitapp/index.htm http://www.allenbrowne.com/ser-01.html |
#6
| |||
| |||
|
|
You can speed up the forms if you open and maintain a persistent connection to the backend database. I do this in the "splash screen" form (my "startup" form) by running code in its Timer event that opens a hidden form that is based on a dummy table in the backend. This maintains a persistent connection so that the front end does not need to continually test and delete and open an . ldb file for the backend for that front end. |
#7
| |||
| |||
|
|
You can speed up the forms if you open and maintain a persistent connection to the backend database. I do this in the "splash screen" form (my "startup" form) by running code in its Timer event that opens a hidden form that is based on a dummy table in the backend. This maintains a persistent connection so that the front end does not need to continually test and delete and open an . ldb file for the backend for that front end. |
#8
| |||
| |||
|
|
You can speed up the forms if you open and maintain a persistent connection to the backend database. I do this in the "splash screen" form (my "startup" form) by running code in its Timer event that opens a hidden form that is based on a dummy table in the backend. This maintains a persistent connection so that the front end does not need to continually test and delete and open an . ldb file for the backend for that front end. |
#9
| |||
| |||
|
|
Thanks Ken I have been having trouble sending a reply - as you can see I'll try again but what I am trying to say is that this is a bit too technical for me On Wed, 10 Aug 2005 18:37:05 -0400, "Ken Snell" kthsneisllis9 (AT) ncoomcastt (DOT) renaetl> wrote: You can speed up the forms if you open and maintain a persistent connection to the backend database. I do this in the "splash screen" form (my "startup" form) by running code in its Timer event that opens a hidden form that is based on a dummy table in the backend. This maintains a persistent connection so that the front end does not need to continually test and delete and open an . ldb file for the backend for that front end. |
|
« Previous Thread
|
Next Thread »
| Thread Tools | |
| Display Modes | |
Linear Mode
| |
Powered by vBulletin Version 3.5.3
Copyright ©2000 - 2012, Jelsoft Enterprises Ltd.
Copyright ©2000 - 2012, Jelsoft Enterprises Ltd.