Migrating from mdb to ADP: dbengine.idle dbRefreshcache

[Mark]

Hi

Using Access XP (with integrated windows security), MSDE and a very very
slow network.

I am migrating a small mdb to ADP and have many instances where I use
"dbEngine.Idle dbRefreshCache" etc.

When I use this in the ADP I am getting prompted for a (Workgroup) login
etc. As far as I can tell this only happens the first time.

I have two questions then:

First: Is it necessary to use "dbEngine.Idle dbRefreshCache" when working
with an MSDE backend?

And second: If the answer to the first question is yes then how do I prevent
the login dialog popping up?

Thanks very much

Mark

 

[Sylvain Lafontaine]

No, it's not necessary to use it for MSDE and regular ADO commands or when
you have created a DBEngine to issue DAO commands against the MSDE database.

However, if you have openened a MDB, then of course you must use it if
necessary (ie. this MDB file is not opened for your exclusive use and other
people use it, too).

 

[Mark]

Thanks Sylvian )

No, it's not necessary to use it for MSDE and regular ADO commands or when
you have created a DBEngine to issue DAO commands against the MSDE
database.

However, if you have openened a MDB, then of course you must use it if
necessary (ie. this MDB file is not opened for your exclusive use and
other people use it, too).

 

[david epsom dot com dot au]

MSDE uses a different cache, and a different login.

It is interesting that you are getting prompted for
a workgroup login when you refresh the Jet data cache,
but if the engine hadn't had to log in previously,
then there can't be anything in that cache worth
refreshing.

(david)