(Msg. 1) Posted: Wed Jun 18, 2008 5:53 am
Post subject: Corruption Problem with 2.0 Archived from groups: microsoft>public>access (more info?)
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
(Msg. 2) Posted: Wed Jun 18, 2008 6:45 am
Post subject: Re: Corruption Problem with 2.0 [Login to view extended thread Info.] Archived from groups: per prev. post (more info?)
On Wed, 18 Jun 2008 05:53:00 -0700, Louise54
<Louise54 DeleteThis @discussions.microsoft.com> wrote:
You should upgrade the BE to the least common denominator, which you
state is A2000.
There is no point in having 2 databases; 86MB is peanuts.
For corruption tips check this out:
http://www.granite.ab.ca/access/corruptmdbs.htm
-Tom.
>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
(Msg. 3) Posted: Wed Jun 18, 2008 6:56 am
Post subject: RE: Corruption Problem with 2.0 [Login to view extended thread Info.] Archived from groups: per prev. post (more info?)
At times like this, nothing beats a good backup. In fact make a complete
backup of your database now and put it away for safe keeping. I suggest daily
backups until you can figure out the problem.
I'm wondering what has changed in the last few weeks on the network. Have
they installed any new equipment? Possibly some of the old equipment is
failing such as a switch, router, cable, or network interface card (NIC). See
if your network people can run a sniffer for bad packets. That can cause
corruption.
I have a white paper in a Word document named Fix Corrupt Access Database
towards the bottom this page:
http://www.rogersaccesslibrary.com/OtherLibraries.asp
--
Jerry Whittle, Microsoft Access MVP
Light. Strong. Cheap. Pick two. Keith Bontrager - Bicycle Builder.
"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
(Msg. 4) Posted: Wed Jun 18, 2008 11:24 am
Post subject: Re: Corruption Problem with 2.0 [Login to view extended thread Info.] Archived from groups: per prev. post (more info?)
>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.
I'm with Tom and Jerry. 86 Mb is peanuts. Convert to A2000 your
lowest common denominator.
And see if discussions with your IT department can figure out what's
new in the last three weeks. New PC? Or what.
Tony
--
Tony Toews, Microsoft Access MVP
Please respond only in the newsgroups so that others can
read the entire thread of messages.
Microsoft Access Links, Hints, Tips & Accounting Systems at
http://www.granite.ab.ca/accsmstr.htm
Tony's Microsoft Access Blog - http://msmvps.com/blogs/access/
(Msg. 5) Posted: Wed Jun 18, 2008 12:13 pm
Post subject: Re: Corruption Problem with 2.0 [Login to view extended thread Info.] Archived from groups: per prev. post (more info?)
THanks everyone. We added two new things in the last month. The first being a
new phone system, but not sure how that would affect anything in regards to
this database? Second is a managed ops service, but I questioned whether
anything may be a conflict there and they don't seem to think so.
Otherwise, no new pcs or servers.
When I make the conversion to 2000, can I do one table at a time and just
make the re-link to each table as I add them in? Or should I do the entire
database at once?
Also, can I jump directly from 2.0 to 2000? Best procedures to handle
auto-number fields?
Thanks so much!
Louise
"Tony Toews [MVP]" wrote:
> Louise54 <Louise54 DeleteThis @discussions.microsoft.com> wrote:
>
> >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.
>
> I'm with Tom and Jerry. 86 Mb is peanuts. Convert to A2000 your
> lowest common denominator.
>
> And see if discussions with your IT department can figure out what's
> new in the last three weeks. New PC? Or what.
>
> Tony
> --
> Tony Toews, Microsoft Access MVP
> Please respond only in the newsgroups so that others can
> read the entire thread of messages.
> Microsoft Access Links, Hints, Tips & Accounting Systems at
> http://www.granite.ab.ca/accsmstr.htm > Tony's Microsoft Access Blog - http://msmvps.com/blogs/access/ >
(Msg. 6) Posted: Wed Jun 18, 2008 3:49 pm
Post subject: Re: Corruption Problem with 2.0 [Login to view extended thread Info.] Archived from groups: per prev. post (more info?)
>When I make the conversion to 2000, can I do one table at a time and just
>make the re-link to each table as I add them in? Or should I do the entire
>database at once?
No, convert the entire MDB. It will only take a few or thirty
seconds. Besides converting one table at a time would lose
referential integrity.
>Also, can I jump directly from 2.0 to 2000?
Yes. If directly converting doesn't work then create a new MDB and
import the tables. Although you will lose the layout of the
relationships window.
>Best procedures to handle auto-number fields?
Nothing to handle. Those will convert just fine. Or am I missing
something here?
Tony
--
Tony Toews, Microsoft Access MVP
Please respond only in the newsgroups so that others can
read the entire thread of messages.
Microsoft Access Links, Hints, Tips & Accounting Systems at
http://www.granite.ab.ca/accsmstr.htm
Tony's Microsoft Access Blog - http://msmvps.com/blogs/access/
(Msg. 7) Posted: Wed Jun 18, 2008 5:12 pm
Post subject: Re: Corruption Problem with 2.0 [Login to view extended thread Info.] Archived from groups: per prev. post (more info?)
Regarding the auto-number fields: they will remain the same once converted,
and then pick up reassigning where it left off? Maybe I'm thinking of what
happens when you import old data into new tables (not just convert them).
"Tony Toews [MVP]" wrote:
> Louise54 <Louise54.RemoveThis@discussions.microsoft.com> wrote:
>
> >When I make the conversion to 2000, can I do one table at a time and just
> >make the re-link to each table as I add them in? Or should I do the entire
> >database at once?
>
> No, convert the entire MDB. It will only take a few or thirty
> seconds. Besides converting one table at a time would lose
> referential integrity.
>
> >Also, can I jump directly from 2.0 to 2000?
>
> Yes. If directly converting doesn't work then create a new MDB and
> import the tables. Although you will lose the layout of the
> relationships window.
>
> >Best procedures to handle auto-number fields?
>
> Nothing to handle. Those will convert just fine. Or am I missing
> something here?
>
> Tony
> --
> Tony Toews, Microsoft Access MVP
> Please respond only in the newsgroups so that others can
> read the entire thread of messages.
> Microsoft Access Links, Hints, Tips & Accounting Systems at
> http://www.granite.ab.ca/accsmstr.htm > Tony's Microsoft Access Blog - http://msmvps.com/blogs/access/ >
(Msg. 8) Posted: Wed Jun 18, 2008 5:27 pm
Post subject: Re: Corruption Problem with 2.0 [Login to view extended thread Info.] Archived from groups: per prev. post (more info?)
To ease your concerns, you should always backup your data to a safe
location with a differently named MDB. That way you'll have an
ironclad fallback.
Your autonumbers won't miss a beat. They're no more at risk than any
other data.
HTH
--
-Larry-
--
"Louise54" <Louise54.RemoveThis@discussions.microsoft.com> wrote in message
news:C46AD54D-AA6F-431C-A124-643FB0157FB6@microsoft.com...
> Regarding the auto-number fields: they will remain the same once
converted,
> and then pick up reassigning where it left off? Maybe I'm thinking
of what
> happens when you import old data into new tables (not just convert
them).
>
>
>
> "Tony Toews [MVP]" wrote:
>
> > Louise54 <Louise54.RemoveThis@discussions.microsoft.com> wrote:
> >
> > >When I make the conversion to 2000, can I do one table at a time
and just
> > >make the re-link to each table as I add them in? Or should I do
the entire
> > >database at once?
> >
> > No, convert the entire MDB. It will only take a few or thirty
> > seconds. Besides converting one table at a time would lose
> > referential integrity.
> >
> > >Also, can I jump directly from 2.0 to 2000?
> >
> > Yes. If directly converting doesn't work then create a new MDB
and
> > import the tables. Although you will lose the layout of the
> > relationships window.
> >
> > >Best procedures to handle auto-number fields?
> >
> > Nothing to handle. Those will convert just fine. Or am I
missing
> > something here?
> >
> > Tony
> > --
> > Tony Toews, Microsoft Access MVP
> > Please respond only in the newsgroups so that others can
> > read the entire thread of messages.
> > Microsoft Access Links, Hints, Tips & Accounting Systems at
> > http://www.granite.ab.ca/accsmstr.htm > > Tony's Microsoft Access Blog - http://msmvps.com/blogs/access/ > >
All times are: Eastern Time (US & Canada) (change) Goto page 1, 2, 3, 4
Page 1 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
Home
Forums
Home
FAQ
Profile
Private Messages
Log in
Office Other