Access 2002 messed up my app! (OK, that's too strong. I should say
that A2002 seems to have changed the functionality of the
OpenCurrentDatabase method. So now my application is kindof *messy*).
Let me explain:
I have an app that exports some tables from the current DB to another
one on a floppy with the following code:
Dim objAccess As New Access.Application
.DoCmd.TransferDatabase acExport, "Microsoft Access", _
strDBTo, acTable, strTableNameSource, strTableNameDest
This has been working fine in Access2K. (It loops through this
procedure a number of times for each table exported.)
The problem is that recently I needed to put the app on a machine
running Access2002. NOW, when the app loops through this code, the
openCurrentDatabase function actually OPENS up a NEW window with a
second copy of the current DB, then it CLOSES again. The effect of
this is a very unsightly *flashing* on and off of new windows as the
code loops through this procedure.
This is rather irritating, so if someone would be so kind as to
explain why this happens in 2002 & not 2K (and what I might do about
it) I would greatly appreciate it!
P.S. I'm something of a beginner in Access, so perhaps the way I did
this in A2K wasn't the best way. (But it DID work!) If there is
another, more efficient or preferable method to do this, I'd certainly
like to know!