[AccessD] OpenRecordSet question

Max Wanadoo max.wanadoo at gmail.com
Sun Aug 9 16:54:25 CDT 2009


When have  I ever know that??

Sometimes I am not even sure who I am.

Thanks for the info though.


Elvis



-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Gustav Brock
Sent: 09 August 2009 22:48
To: accessd at databaseadvisors.com
Subject: Re: [AccessD] OpenRecordSet question

Hi Max

Well ... no. That certainly depends. You just need to know what you are
doing.

/gustav

>>> max.wanadoo at gmail.com 09-08-2009 18:05:05 >>>
Thanks Gustav.
I think the later posts from Stuart clarify the situation.
Back to good old CurrentDB then.
Max


-----Original Message-----
From: accessd-bounces at databaseadvisors.com 
[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Gustav Brock
Sent: 09 August 2009 11:36
To: accessd at databaseadvisors.com 
Subject: Re: [AccessD] OpenRecordSet question

Hi Max

A surprise is waiting you. Try to, say, create a table by calling another
function and read it from your db object; it isn't there until you do a
db.Refresh. So:

.. you ARE actually looking at the DB object as is when initialized or
refreshed - including subsequent changes made in the current context.

/gustav

>>> max.wanadoo at gmail.com 09-08-2009 12:03 >>>
Very interesting John,

FWIW my results hover around the 150 mark ??  DBENGINE is 1.

So, clearly the answer is to Set db = DBEngine(0)(0).  That way you will
know that you ARE actually looking at the DB as it exists and not as it DID
exist at the time when the object was created.

Thanks for the effort.

Max


-- 
AccessD mailing list
AccessD at databaseadvisors.com
http://databaseadvisors.com/mailman/listinfo/accessd
Website: http://www.databaseadvisors.com




More information about the AccessD mailing list