Hi,
Getting the above error after a few changes of data, but not immediately.
Not changed or done anything different (perhaps a Windows update a few days ago but sure fine since then)
Windows 10 on all PC's. All been fine & 100% for years (never had corruption)
Access 2007. Full ms access version installed on two main PC's. started with test.accde/runtime switch
3 PC's
Main PC #1 Front End is fine & works no matter what
The back end is on this Main PC #1 and listed as local drive d:/ etc etc.
PC #2 is on wired gigabit network & this is solid.
FE points to BE with \\office\ etc etc.
Now if PC #1 program is running and I then use PC #2 I get the error above
Can sometimes start with Error 3040 Disk I/O but straight after 3343.
And can be a few minutes of using before it fails??
If PC #1 FE is NOT running, PC #2 is fine, still accessing the network BE 100% fine.
I have re-linked the BE, compacted & repaired, fresh import of the BE data into a new DB.
Oddly PC #3 is at another location and seems to work fine with PC #1 FE open. This has just a runtime version. The reference all seem fine & the same VB6. I don't think this PC has had the Windows 10 update yet.
As a note & this was a few week back and been fine for a couple of weeks PC #3 was changed briefly and being runtime I struggled to get reference working. It ended up having VB7 (other VB6). This worked fine. The original PC is back now. This set up and been the same & fine for prob 3 years.
I can't think what to try?
All database I have run diagnostics, all OK.
Done the basic windows scan disk.
Is there a way to repair/install without the original CD, bit reluctant to put the old CD in as sure once thought it put some old stuff on. All legit & registered but not done this for years.
Any advise please.
Thanks I/A
Getting the above error after a few changes of data, but not immediately.
Not changed or done anything different (perhaps a Windows update a few days ago but sure fine since then)
Windows 10 on all PC's. All been fine & 100% for years (never had corruption)
Access 2007. Full ms access version installed on two main PC's. started with test.accde/runtime switch
3 PC's
Main PC #1 Front End is fine & works no matter what
The back end is on this Main PC #1 and listed as local drive d:/ etc etc.
PC #2 is on wired gigabit network & this is solid.
FE points to BE with \\office\ etc etc.
Now if PC #1 program is running and I then use PC #2 I get the error above
Can sometimes start with Error 3040 Disk I/O but straight after 3343.
And can be a few minutes of using before it fails??
If PC #1 FE is NOT running, PC #2 is fine, still accessing the network BE 100% fine.
I have re-linked the BE, compacted & repaired, fresh import of the BE data into a new DB.
Oddly PC #3 is at another location and seems to work fine with PC #1 FE open. This has just a runtime version. The reference all seem fine & the same VB6. I don't think this PC has had the Windows 10 update yet.
As a note & this was a few week back and been fine for a couple of weeks PC #3 was changed briefly and being runtime I struggled to get reference working. It ended up having VB7 (other VB6). This worked fine. The original PC is back now. This set up and been the same & fine for prob 3 years.
I can't think what to try?
All database I have run diagnostics, all OK.
Done the basic windows scan disk.
Is there a way to repair/install without the original CD, bit reluctant to put the old CD in as sure once thought it put some old stuff on. All legit & registered but not done this for years.
Any advise please.
Thanks I/A