WUGNET, the Windows User Group Network
Your Complete Resource Center for "The Best" in Shareware, Computing Tips and Support, Windows Industry News... and much more!
Home Forums Shareware Windows Tips Hot Offers FREE Newsletters Arcade Contact Us About Partners
Search WUGNET: RSS Feeds RSS Feeds Advertise with WUGNET    |    Shareware eBooks
HomeHome FAQFAQ      ProfileProfile    Private MessagesPrivate Messages   Log inLog in

Corruption Problem with 2.0

 
Goto page Previous  1, 2, 3, 4
   Home -> Office other -> General Discussions RSS
Next:  Modify numbers  
Author Message
cgiandoni

External


Since: Oct 06, 2008
Posts: 1



(Msg. 25) Posted: Mon Oct 06, 2008 2:14 pm
Post subject: Re: Corruption Problem with 2.0 [Login to view extended thread Info.]
Archived from groups: microsoft>public>access (more info?)

"Louise54" <Louise54.RemoveThis@discussions.microsoft.com> escreveu na notícia da
mensagem:FD9F0FF5-5C0B-44F5-BD47-6F3277E45D7F@microsoft.com...
> Thank you LeeG! This was certainly our problem, and we were at our wits
> end
> trying to figure out what was causing it. Just saw your reply two days
> ago,
> and after immediately installing the hotfix, we have gone two straight
> days
> without an issue - something that hasn't occurred since late May!
> Once again, thank you for taking the time to provide me with this
> information!
> Louise
>
> "LeeG" wrote:
>
>> An issue was introduced with WinXp XP3 as well as a security update
>> Microsoft
>> shipped in late May (MS08-028 / KB950749) that is causing the issue you
>> are
>> experiencing. Call Microsoft Customer Support and request hotfix
>> KB954193.
>>
>> "Louise54" wrote:
>>
>> > I have a multi-user (approx 8 people) on a back-end 2.0 database which
>> > is
>> > currently about 86,000KB in size. They each have a front end on their
>> > local
>> > hard drive, using whatever Access version is on their pc (from 2000 up
>> > to
>> > 2007). The backend has been working just fine for several years until a
>> > few
>> > weeks ago.
>> >
>> > In the last 3 weeks we've been getting "unrecognized database format"
>> > errors
>> > (7 times total). I've been able, thus far, to repair/compact, but it's
>> > taking
>> > longer each time. I'm running through various checks to see if I can
>> > find the
>> > cause.
>> >
>> > At the same time, I think it's probably time to bite the bullet and
>> > convert
>> > the back end to a higher version. I know this has been discussed many
>> > times,
>> > but is there a favorite set of procedures to do this conversion? And a
>> > version more stable than others that I should move to? We don't have
>> > that
>> > many tables, but I think the biggest headache for me will be dealing
>> > with
>> > several auto-number fields. Also, is it ok to have two backend
>> > databases?
>> > Because of size restrictions, I thought it might be better to split the
>> > one
>> > backend into two this time?
>> >
>> > Any and all help, comments, suggestions would be greatly appreciated.
>> > Thank
>> > you!
>> > Louise
Back to top
Login to vote
Display posts from previous:   
       Home -> Office other -> General Discussions All times are: Eastern Time (US & Canada) (change)
Goto page Previous  1, 2, 3, 4
Page 4 of 4

 
You can post new topics in this forum
You can reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
Categories:
 Windows XP
 Windows Vista
 Windows Other
 Office
  Office Other
 Security
 WinRAR
  • Home |
  • Shareware |
  • Windows Tips |
  • Hot Offers |
  • FREE Newsletters |
  • Arcade |
  • Forums |
  • eBooks |
  • About WUGNET |
  • Partners |
  • Contact

  • WUGNET Privacy Policy |
  • Link to WUGNET