Re: Compact & Repair
- From: "Sylvain Lafontaine" <sylvain aei ca (fill the blanks, no spam please)>
- Date: Thu, 10 May 2007 12:08:14 -0400
Each user must have his/her own copy of the mdb file; otherwise, difference
in versions of Windows on each console will corrupt the database. You could
also try to disable the Op-Lock on the server:
http://support.microsoft.com/kb/300216
http://support.microsoft.com/kb/296264
but the real solution is for each user to have his own copy. Finally, you
should also ask this kind of question in a newsgroup about linked tables
such as m.p.access.odbcclientsvr .
--
Sylvain Lafontaine, ing.
MVP - Technologies Virtual-PC
E-mail: sylvain aei ca (fill the blanks, no spam please)
"mfm" <mfm@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:73CBDBEC-E081-447A-A7C8-66F68E2030BB@xxxxxxxxxxxxxxxx
so oftoenWe run an Access 2003 database. Some of the tables are linked to
a
SQL Server 2000 database located on the same server that the .mdb file
resides. We have always had issues where, during the day, when someone
would
get a message saying that the database needs to be repaired. Thus we
would
get everybody out, compant & repair, and then they would be ok until the
next
time this happened. We recently migrated to a new server (2003.) It
seems
as though this is now happening more frequently. The .mdb is only 101 MB,
however we have between 20 and 30 users running in the system at any given
point during the day. Is there anything I can do to prevent having to
'compact & repair'? Any ideas appreciated. I
.
- Prev by Date: Re: Error sending date variable to Stored Procedure
- Next by Date: Re: Pass-through to stored procedure
- Previous by thread: SQL Server 2005 Express
- Next by thread: implicit conversion datetime error
- Index(es):
Relevant Pages
|
