Duplicate DB

[Tim]

I have 2 Databases (one of them is just a copy of the
other one). The first one contains list of active
membership, the second one contains cancelled membership
clients. When a client cancels a membership, he/she needs
to be deleted of the first DB and copied to the second DB.
I've been doing this from a scratch, typing all notes from
main and subforms of the 1st DB to the 2nd. Is there any
other way to do this?

 

[Cheryl Fischer]

Tim,

I believe you will have a better, more flexible application and a lot less
work if you do away with the separate database for Cancelled members and
keep all of your membership records in the same table. In the table
containing your membership records, add a field named: Cancelled (Yes/No
type). You might also want CancellationDate and CancellationReason.

Your reports and queries can always be written to exclude records where
Cancelled = True


hth,

 

[Tim]

Thanks Cheryl,
I thougth that way too, but I was afraid of growing size
of the DB and it's my last option. So far I got about 1600
clients with corresponding notes in subforms and it will
grow. I'm not sure how much data can hold the access DB.
Size of the DB is 12.0 MB. Another reason to keep 2 DBs is
we rarely use or access the second DB.

 

[Cheryl Fischer]

Tim,

You have a long way to go before you hit "the wall". An Access 97 database
will max out at 1 GB; the maximum size of a database in Access 2000 and
newer is 2 GB.

And, of course, your application should be split into two databases as
follows: A front-end containing all Queries, Forms, Reports, Macros and
Modules and a back-end containing only shared data Tables. The front-end
links to tables in the back-end using File|Get External Data|Link.
Regularly compacting the back-end will minimize bloat and generally keep the
db healthy.

 

[Tim]

Cheryl, you inspired me. My DB's (Access2000) are not
split yet, I haven't gotten so far and I don't know how to
do it. But I'll dig into it, and if I have questions, I
post it in the newsgroup. Speaking of the health, my DB is
corrupted and I'm getting all sort of messages such
as 'disk or network error' on users PCs in random. I'm
working on it too. Hope, splitting the DBs helps to fix
them.
Thank you,

 

[Cheryl Fischer]

Tim,

As regards corruption of databases, Access MVP Tony Toews has put together a
compilation of diagnoses, solutions and other information about database
corruption and its avoidance at:

http://www.granite.ab.ca/access/corruptmdbs.htm

 

[Tim]

Thanks again Cheryl,
This is what I need...

-----Original Message-----
Tim,

As regards corruption of databases, Access MVP Tony Toews has put together a
compilation of diagnoses, solutions and other information about database
corruption and its avoidance at:

http://www.granite.ab.ca/access/corruptmdbs.htm

--

Cheryl Fischer, MVP Microsoft Access
Law/Sys Associates, Houston, TX





.