VBA, User Define Type Not Defined

User Define Type Not Defined

Author	Message
Jim Kilg #1 / 4	User Define Type Not Defined I keep getting a compile error when I attempt to run a VBA Sub that I created. Here is the code where the error occurs. Dim db As Database I get a compile error message box that says "User Define Type Not Defined". I am new to VBA so any help would be wonderful TIA Jim
Thu, 21 Nov 2002 03:00:00 GMT

Jim Kilg #2 / 4	User Define Type Not Defined Work great! Thanks from a newbie to VBA...I'm learning! See ya - Jim Quote: > On Sun, 4 Jun 2000 14:49:33 -0400, "Jim Kilgo" > >I keep getting a compile error when I attempt to run a VBA Sub that I > >created. Here is the code where the error occurs. > >Dim db As Database > [snip] > If you use Access 2000 to create a new database, it assumes you want > to use the ADO object model. The ADO object model doesn't expose a > Database object; the DAO object model does. > Open any module in design view. Open the References dialog (Tools \| > References). Check the reference for DAO 3.6, and (perhaps) remove > the check for ADO (Activex Data Objects). (At least lower its > priority.) > -- > Mike Sherrill > Information Management Systems
Fri, 22 Nov 2002 03:00:00 GMT

Allen Brown #3 / 4	User Define Type Not Defined From the code window, Tools \| References. Look for anything marked "Missing". Quote: > I keep getting a compile error when I attempt to run a VBA Sub that I > created. Here is the code where the error occurs. > Dim db As Database > I get a compile error message box that says "User Define Type Not Defined". > I am new to VBA so any help would be wonderful -- Perth, Western Australia Tips for MS Access users at: http://odyssey.apana.org.au/~abrowne
Sun, 24 Nov 2002 03:00:00 GMT

MSherr.. #4 / 4	User Define Type Not Defined On Sun, 4 Jun 2000 14:49:33 -0400, "Jim Kilgo" Quote: >I keep getting a compile error when I attempt to run a VBA Sub that I >created. Here is the code where the error occurs. >Dim db As Database [snip] If you use Access 2000 to create a new database, it assumes you want to use the ADO object model. The ADO object model doesn't expose a Database object; the DAO object model does. Open any module in design view. Open the References dialog (Tools \| References). Check the reference for DAO 3.6, and (perhaps) remove the check for ADO (Activex Data Objects). (At least lower its priority.) -- Mike Sherrill Information Management Systems
Sun, 24 Nov 2002 03:00:00 GMT

Page 1 of 1

[ 4 post ]