Maximum Revisions?

[Earl Partridge]

Access 2000
I was informed a while back (perhaps in this newsgroup) that there is a maximum number
of revisions that can be made to an Access database. What is that number, and is there
some place in Access I can find the total revisions made?
Earl

 

[Allen Browne]

That's not correct, Earl.

If you keep adding and removing things (such as fields in a table, or text
boxes on a form) without compacting to remove the old ones, you can run into
a wall. Run a compact delete the old stuff. If necessary, create a new
database and import the objects. Or if you are really stuck you can
SaveAsText/LoadFromText.

To learn about some of those techniques, and how to recover a database that
has hit problems, see:
http://allenbrowne.com/recover.html

 

[a a r o n _ k e m p f]

1. Only 1 person can make 1 change at a time with Jet.

If you just lost the training wheels and moved to Access Data
Projects, then you could hire multiple developers.

 

[John W. Vinson]

1. Only 1 person can make 1 change at a time with Jet.

False.

 

[George]

Perhaps it should not need to be pointed out yet again, but flat assertions
of the sort that include the words "can" or "can't" -- and their close
cousins, "must" and "must not" -- tend to be dangerous to the credibility of
the person making such assertions because they are so often wrong, and so
easily refuted. Consider the instant case.

One of the inherent problems with developing in Access is that it is INDEED
very possible for two (or more) people to make two (or more) changes to the
same mdb at the same time. And that is a potential problem for which any
competent development team must account in its development protocols.

In fact, one of the SOLUTIONS to this potential problem lies precisely in
creating a development protocol through which only one person has authority
to implement changes to a particular object in a "master"copy of an mdb at
any given time.

But then, wouldn't that be a desirale approach in any other development
environment, as well?


1. Only 1 person can make 1 change at a time with Jet.

If you just lost the training wheels and moved to Access Data
Projects, then you could hire multiple developers.

 

[a a r o n _ k e m p f]

John;

Jet was designed as a single user application.
Only one person can edit tables / queries at the same time.

If you only have one developer / analyst / admin-- this might fit your
needs.
But most of the companies that I've worked with over the past decade--
have more than one person that needs to write queries.

Instead of making excuses-- it would be best for you to move to SQL
Server and Access Data Projects

 

[jd]

Perhaps it should not need to be pointed out yet again, but flat
assertions of the sort that include the words "can" or "can't" -- and
their close cousins, "must" and "must not" -- tend to be dangerous to the
credibility of the person making such assertions because they are so often
wrong, and so easily refuted. Consider the instant case.

One of the inherent problems with developing in Access is that it is
INDEED very possible for two (or more) people to make two (or more)
changes to the same mdb at the same time. And that is a potential problem
for which any competent development team must account in its development
protocols.

In fact, one of the SOLUTIONS to this potential problem lies precisely in
creating a development protocol through which only one person has
authority to implement changes to a particular object in a "master"copy of
an mdb at any given time.

But then, wouldn't that be a desirale approach in any other development
environment, as well?


1. Only 1 person can make 1 change at a time with Jet.

If you just lost the training wheels and moved to Access Data
Projects, then you could hire multiple developers.

 

[Gina Whipp]

Earl,

I have databases created in Access 97 that I am STILL making
additions/changes/updates/revisions to. So, I'm going to say with some
degree of comfort, if there is a maximum number I haven't reached it yet and
my odds are pretty good that I'm not even close. Hopefully, someone WILL
have the exact number for you (and me too since I don't remember it either.)

F.Y.I., please ignore Aaron's post as he feels the need to shoot down Jet at
every ooportunity he gets!

--
Gina Whipp

"I feel I have been denied critical, need to know, information!" - Tremors
II

http://www.regina-whipp.com/index_files/TipList.htm

 

[Paul Shapiro]

I sort of remember a limit of 1024 or so revisions to any database object
(forms, reports, maybe modules). But I think you can escape the limit either
using source code control, which builds the db new from the saved text files
whenever you want, or by using the undocumented Application.SaveAsText and
..LoadFromText (which might not be the exact method names) to recreate any
objects as needed.