-
February 17th, 2005, 01:29 PM
#1
Disk or Network Error
When I try to open a large database (40,000 records) on one of my applications and order it by a non-index field I receive a run-time error 3043 "Disk or Network Error". The debugger stops on opening the recordset. I'm using DAO. If I order by an indexed field their is no problem. If the recordset is 9000 records then their is no problem. I have a couple of other applications that use the same type of code and work just fine when ordering by indexed or non-indexed field regardless of record size. In reserching this error on the Internet it appears to be associated with running apps off of a server. My application is running on a single PC, no server involved. Also, it only occurs on a Windows 2K PC. Works without problems on Win 98 and XP PCs that I have tested with. Does anyone have any idea on the problem or what I should try for isolating it? Thanks.
-
February 18th, 2005, 04:07 AM
#2
Re: Disk or Network Error
What version of Access are you using? 97 / 2000 or later?
Is your setup an EXE connecting to an Access database, all on the same machine?
-
February 18th, 2005, 04:40 AM
#3
Re: Disk or Network Error
Hello!
I faced this problem earlier while working with Access database. In my case this problem occurred when hard disk (in which database is located) goes out of space.
-
February 18th, 2005, 08:30 AM
#4
Re: Disk or Network Error
The database is Access XP and it is on the same PC. Upon further testing, the problem only occurs when going to runtime with VB. If I compile the program and run the exe from the same folder there is no problem. So it looks like the end user will not see this problem and therefore a solution would be nice but not essential.
-
February 18th, 2005, 08:49 PM
#5
Re: Disk or Network Error
how much emory does the ide use up when you run this query? how long does it take?
access.. hmm.. have you thought about MSDE?
-
February 19th, 2005, 01:15 PM
#6
Re: Disk or Network Error
As you have mentioned that this issue usually occurs on a server (dealing with the Temp directory
being utilized by Access and other programs). It could be that the system is running low on
resources? Perhaps thats why it fails on large recordsets?
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
|