TransferDatabase Question

[Dkline]

I have code that exports queries in a "source" database as tables to a
"target" database. I run about 20 queries through a function which uses:
DoCmd.TransferDatabase acExport, "Microsoft Access", PathToSource, acTable,
NameOfQuery, NameOfTable, False, False

One of my coworkers has observed that the date/timestamp on the query in the
source database doesn't change to the date when the macro has exported the
query to the other database. The target database does show that all the
tables created by the action of the amcro do have a current date/time stamp.

Is this the way it is supposed to be - that the source's date/time does not
change through this action?

She's a little nervous that the dates of the queries are not changing in the
source. So I'm looking to reassure her that it is working as intended.

 

[Douglas J. Steele]

Are you asking whether the date changes in the source database simply
because you've exported to another database? You haven't made any change to
the query, so why should the date change? If you copy a file, the file's
Last Updated date doesn't change either.

 

[Dkline]

After stewing on it some more I came to your answer.

I guess I was being thrown by the behavior if I simply open the query and
close it without any modification, the date stamp changes. I extended that
result to the TransferDatabase that by running the the code to transfer the
query to a database I would be "opening" the query.