|
-
Aug 29th, 2000, 06:31 PM
#1
Thread Starter
Lively Member
is there any reason why an ado recordset obj would close if you did not code it to close?
-
Aug 29th, 2000, 06:36 PM
#2
Monday Morning Lunatic
Maybe if the provider timed out.
I refuse to tie my hands behind my back and hear somebody say "Bend Over, Boy, Because You Have It Coming To You".
-- Linus Torvalds
-
Aug 29th, 2000, 06:39 PM
#3
Thread Starter
Lively Member
are you referring to "provider" as a network connection? if so using local machine no net conn
-
Aug 29th, 2000, 06:42 PM
#4
Monday Morning Lunatic
No, provider as in the database access provider (such as SQL Server or Access). If you don't keep the connection alive it may timeout and close it.
I refuse to tie my hands behind my back and hear somebody say "Bend Over, Boy, Because You Have It Coming To You".
-- Linus Torvalds
-
Aug 29th, 2000, 06:51 PM
#5
Thread Starter
Lively Member
i think i know where im going wrong,. im using a single object and returning a single record(set) and when i do a new search the old recordset has been replaced with the new one something like that. just gonna take time to convert from dao to ado things are handled a little odder than dao
thnx
Posting Permissions
- You may not post new threads
- You may not post replies
- You may not post attachments
- You may not edit your posts
-
Forum Rules
|
Click Here to Expand Forum to Full Width
|