Migrating from mdb to ADP: dbengine.idle dbRefreshcache

Thread view:

Enable EMail Alerts

Start New Thread

Thread rating:

Mark - 22 Feb 2006 11:37 GMT

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

Reply to this Message

Sylvain Lafontaine - 22 Feb 2006 14:49 GMT

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).

Signature

Sylvain Lafontaine, ing.
MVP - Technologies Virtual-PC
E-mail: http://cerbermail.com/?QugbLEWINF

> Hi
>
[quoted text clipped - 18 lines]
>
> Mark

Reply to this Message

Mark - 22 Feb 2006 20:10 GMT

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
[quoted text clipped - 26 lines]
>>
>> Mark

Reply to this Message

david epsom dot com dot au - 24 Feb 2006 07:26 GMT

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)

> Hi
>
[quoted text clipped - 18 lines]
>
> Mark

Reply to this Message