Modified Date

[Russell]

I'm looking for a quick and dirty way to change the
modified date on some tables after an Import routine. I
used to run some code that would execute some Make Table
queries, but that keep my database bloated. Now I'm using
a series of Delete and Append queries, but that doesn't
effect the modified date. I was using the modified date
for some validations. Any ideas?

Thanks,
Russell

 

[Wayne Morgan]

You should be able to handle the bloat by compacting the database after
you're done, as long as you don't keep a bunch of unused tables in the file.
The modified date of the table is when the structure of the table was
changed, not the data in it. The only thing I can think of to force a change
would be to do something, such as add a field and delete it again. It would
probably be better to have a date field in the table that stores the date
that the data was added.

 

[Russell]

Both those ideas seem good and should work fine I think.

RE: Compacting. The database runs big all the time because
of the amount of data, sometimes a compete import process
pushes it over the maximum size limit and I'd never get to
the compact part of the code. We also have a few stray
users that leave the database up over night and that would
stop the compact in its track as well.

Anyway, thanks for your help!

 

[Wayne Morgan]

Unless disk space is a problem, its maximum size limit is 2GB. If you're
pushing that, it may be time to consider SQL Server.

 

[Larry Daugherty]

You haven't given the specifics of "modified" so no one can confidently
resolve your issue. How about posting back with comprehensive examples of
"modified" dates and your desired results? A big issue is whether all of
the dates in that field are modified..

HTH

 

[Jim Carlock]

Just something interesting that I've noted.

Two .mdb files:
mdb1.mdb Access Version 1
mdb2k.mdb

mdb2k.mdb has some links to mdb1.mdb.
mdb2k.mdb has a make table query that copies the information from
mdb1.mdb to a new table inside mdb2k.mdb.

The Modified Date on mdb1.mdb is updated when the make
table query is run.

Doesn't make sense to me. But its happening.

--
Jim Carlock
http://www.microcosmotalk.com/
Post replies to the newsgroup.


Both those ideas seem good and should work fine I think.

RE: Compacting. The database runs big all the time because
of the amount of data, sometimes a compete import process
pushes it over the maximum size limit and I'd never get to
the compact part of the code. We also have a few stray
users that leave the database up over night and that would
stop the compact in its track as well.

Anyway, thanks for your help!