Group:  Microsoft Access ยป microsoft.public.access.gettingstarted
Thread: Front End Corruption

DotNetBag
.NET Development Newsgroups

HTVi
TV Discussion Newsgroups

Our Hot Pick: Rising Antivirus 2006 - Certified by TUV & Checkmark! Get 10% discount by entering this coupon code: ONDISCOUNT10
Rising Antivirus 2006

Front End Corruption
Dj 07.08.2006 16:19:02
I have a split DB that recently started corruping on the front end (it
happened twice). Will running an MDE resolve that issue? Thx, Dj
Re: Front End Corruption
Armen Stein <ArmenStein[ at ]R3m00v3Th1s.gmail.com> 09.08.2006 20:55:39
In article <567550D3-C319-40D5-A02B-97103F43D183[ at ]microsoft.com>,
Dj[ at ]discussions.microsoft.com says...
[Quoted Text]
> I have a split DB that recently started corruping on the front end (it
> happened twice). Will running an MDE resolve that issue? Thx, Dj
>

It might. But you should first ensure that only one person is using the
front-end at a time. Each user should have their own copy of it.

Also, make sure that Name AutoCorrect (in Tools|Options) is turned off.

Even with a separate front-end for each user, there are some coding
practices that can increase the chance of corruption, like automating
other Office programs and not cleaning up their objects, creating and
deleting front-end database objects, etc.

--
Armen Stein
Microsoft Access MVP
www.JStreetTech.com

Home | Search | Terms | Imprint | Contact
Newsgroups Reader - provided by WiredBox.Net