Creating Recordset Clone

[OldBirdman]

I want to create a RecordsetClone. MS Access Help has an example under "Clone Method Example (MDB)" which has the statement " Dim dbs As Database".
I need clones in several modules, so in a global module I tried "Global dbs As Database"

Seems to me to be similar enough to the example from MS, but I get the message "User-defined type not defined". Changing to "Dim dbs as Database" gets the same error.

I'm not trying to define my own type, only use one defined already by Microsoft.

What am I doing wrong?

OldBirdman

[puppydogbuddy]

I want to create a RecordsetClone. MS Access Help has an example under "Clone Method Example (MDB)" which has the statement " Dim dbs As Database".
I need clones in several modules, so in a global module I tried "Global dbs As Database"

Seems to me to be similar enough to the example from MS, but I get the message "User-defined type not defined". Changing to "Dim dbs as Database" gets the same error.

I'm not trying to define my own type, only use one defined already by Microsoft.

What am I doing wrong?

OldBirdman

Try :
Global dbs As DAO.Database
Dim dbs DAO.Database

[ADezii]

I want to create a RecordsetClone. MS Access Help has an example under "Clone Method Example (MDB)" which has the statement " Dim dbs As Database".
I need clones in several modules, so in a global module I tried "Global dbs As Database"

Seems to me to be similar enough to the example from MS, but I get the message "User-defined type not defined". Changing to "Dim dbs as Database" gets the same error.

I'm not trying to define my own type, only use one defined already by Microsoft.

What am I doing wrong?

OldBirdman

1. To Declare a 'Global' Recordset Object Variable that can be accessed anywhere from within your Application, use the Public Keyword along with the Explicit Library Type as in:
   

   Public rstMain As DAO.Recordset
   Public rstMain As ADODB.Recordset
    

2. You seem to indicate that you will be using 1 'Global' Variable to Reference multiple Clones in your code. This could be a very bad idea depending on your overall logic and is one of the inherent dangers of Globals. If you use a Global Object Variable to refer to a 2nd Clone, the original Reference will be lost.

[OldBirdman]

Thanks both for your replies.

I was NOT trying to create global clones or recordsets, but only a global Database. I thought that my project was a database, so having one reference to it would simplify things. Apparently it doesn't.

I do not understand DAO vs. MDB. Past experience has taught me to use MDB and avoid DAO. Things then work [better]. However, PLEASE do not get into a discussion about that now.

OldBirdman