IWETHEY v. 0.3.0 | TODO
1,095 registered users | 0 active users | 0 LpH | Statistics
Login | Create New User
IWETHEY Banner

Welcome to IWETHEY!

IWETHEY Home / IWETHEY Board / Databases Forum / You're probably all over this, but...
Post #188,500
by Steven A S
Picture of Steven A S
12/29/04 3:27:59 PM
Reply
New You're probably all over this, but...
have you verified that the reference is turned on for 'Microsoft DAO 3.6 Object Library' that it's higher priority than ActiveX Data Objects (I usually turn the latter off altogether)?

Personally, I define my recordset objects within my procedures, and if it's needed in another procedure I'll pass the reference in my parameters. Just remember to 'SET rst = Nothing' at the end of the defining procedure to clear the reference.

And yes I still use DAO regularly myself. I'm just more accustomed to it.
~~~)-Steven----

"I want you to remember that no bastard ever won a war by dying for his country.
He won it by making the other poor dumb bastard die for his country..."

General George S. Patton
Post #188,503
by acagle
12/29/04 3:47:06 PM
Reply
New Re: You're probably all over this, but...
Yeah, I figured that 3.6 stuff out a while ago. I also discovered the original app I borrowed the code from almost does the same thing, but there are pseudo-error traps that keep it from erroring out. But the basic behavior is the same (it pops up the hard-coded error message a couple times before letting you kill it).

So anyway. . . . .the options aren't looking too good unless there's some way to get Access to stop dropping the reference on an error message.
     Access: Runtime error 91. - (acagle) - (22) - Dec. 27, 2004, 02:04:44 PM EST
         I think that one means... - (pwhysall) - (10) - Dec. 27, 2004, 02:17:51 PM EST
             Re: I think that one means... - (acagle) - (9) - Dec. 27, 2004, 02:25:41 PM EST
                 From the 10 Commandments of C Programming: - (inthane-chan) - (8) - Dec. 27, 2004, 02:42:20 PM EST
                     So. - (acagle) - (7) - Dec. 27, 2004, 04:08:09 PM EST
                         In VB? - (JayMehaffey) - (5) - Dec. 27, 2004, 04:37:03 PM EST
                             Re: In VB? - (acagle) - (4) - Dec. 27, 2004, 05:30:43 PM EST
                                 You can use On Error GoTo - (ben_tilly) - (1) - Dec. 27, 2004, 06:29:15 PM EST
                                     That's still the way - (Steven A S) - Dec. 29, 2004, 03:37:21 PM EST
                                 That was a joke - (JayMehaffey) - (1) - Dec. 27, 2004, 07:33:54 PM EST
                                     For certain techniques, it works. - (static) - Dec. 28, 2004, 05:30:48 AM EST
                         Opinions vary on "Global" error checking in VB. - (mmoffitt) - Dec. 30, 2004, 12:26:38 PM EST
         That's the technical term "set" - (FuManChu) - (4) - Dec. 27, 2004, 11:24:31 PM EST
             Re: That's the technical term "set" - (acagle) - (3) - Dec. 28, 2004, 05:28:42 PM EST
                 Yes, unfortunately. - (FuManChu) - Dec. 29, 2004, 02:26:17 AM EST
                 Putting it in every procedure is good practice for VB. - (mmoffitt) - (1) - Dec. 29, 2004, 09:38:14 AM EST
                     Dangitall. - (acagle) - Dec. 29, 2004, 12:23:59 PM EST
         Update: (+edit) - (acagle) - (5) - Dec. 29, 2004, 12:57:53 PM EST
             You're probably all over this, but... - (Steven A S) - (1) - Dec. 29, 2004, 03:27:59 PM EST
                 Re: You're probably all over this, but... - (acagle) - Dec. 29, 2004, 03:47:06 PM EST
             Where is the declaration exactly? And a few more q's. - (mmoffitt) - Dec. 30, 2004, 12:40:15 PM EST
             Did you get this fixed? -NT - (mmoffitt) - (1) - Jan. 3, 2005, 08:33:37 PM EST
                 Re: Did you get this fixed? - (acagle) - Jan. 24, 2005, 05:36:50 PM EST

This country was built on the hope that one day we could all own a Batcave.
110 ms