|
-
Aug 28th, 2001, 08:59 AM
#1
Thread Starter
Frenzied Member
ADO Recordsets
I am accessing a file using ADO. My recrod collection that is returned is large.
The first thing I do is check that I actually have any records, if not then bomb the user out.
The problem I am finding is that when you have a large record collection returned, if you check the recordcount or see whether .EOF = TRUE, it takes AGES to work it out, therefore delaying the flow of my program, and consequently annoying the hell out of the user as they have to sit and wait !!
Is there a way of checking that you have some records returned without having to forego this lengthy wait whilst the program sorts its life out ?
I hope I have explained myself well enough. I caqn supply code if required.
Thanks
Steve.
p.s. I know I posted this question under 'General questions', but I get a quicker response that way
-
Aug 28th, 2001, 09:10 AM
#2
Frenzied Member
I think that the eof or bof are set as soon as you open your recordset so I doubt that they cause the delay. Post your code if you can.
-
Aug 28th, 2001, 09:13 AM
#3
Hyperactive Member
Check the RecordCount property. It wil lreturn 0 if no records found, -1 if there are records, not how many.
FBP

Best Bar.....
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
|