Accessing floppy drive for no reason 1

[ray436]

This is strange......

When I open Access, or especially when resolving conflicts, there is constant polling of the floppy drive.

If the drive is empty this causes MS Access to wait till the PC realizes there is no disk before proceeding. It starts again with each opening of a table, record, etc.

I have never used the floppy drive for storage of anything related to Access.

Besides being extreemly aggravating to say the least, I would like to know why it has started happening. I now leave a blank floppy in the drive just to speed up the process.

Is it my antivirus software? I havent changed it other than to update the signature files, and this just started recently.

Thanks all

Ray

 

[MichaelRed]

Just a quick guess

look for colons (":&quot in any code or queries. Particularlly where it (the colon) is preceded by the letter "a" or "b".



MichaelRed
mred@duvallgroup.com
There is never time to do it right but there is always time to do it over

 

[ray436]

ooooohh...... sneaky, never thought of that!
the hunt is afoot!

Seriously, I'm about ready to pull the A drive from this PC if I don't get this sorted. It adds 5 minutes to what should be a 30 second trip through the database.

I bet you are on to something tho... first look will be in the reformat query that starts the main form.

I'll let you know what I find.

( you're signature line is one of my favorite maxim's )

Ray

 

[TheInsider]

Hi,
There is an exellent add-in utility that I use to search through the database objects for such problems. It is called Find and Replace and you can download it at

http://www.rickworld.com/

Rob Marriott
rob@career-connections.net

 

[ray436]

Thanks guys,
will check out the 'find and replace', looks very useful, especially for those bits of code buried months ago when you did an "on-event" long forgotten about.

Also heard that if I import the whole deal into a blank DB the problem goes away... tried it and its true!

The only snag I have now is I can't compact the silly thing first... it tells me (Admin) I don't have permission. Tried repairing, no dice. All permissions are OK too..

Such is life.

Will use the new imported copy if I have to, but it means alot of work, redirecting all the users, changing settings, etc, etc. oh well.

Thanks again.

Ray

 

[THoey]

Can't you rename the old version to something else and copy the new version into it's old place so you don't have to change links?

Terry M. Hoey
th3856@txmail.sbc.com

Ever notice that by the time that you realize that you ran a truncate script on the wrong instance, it is too late to stop it?

 

[ray436]

I was going to do that, but it seemed waaaay to simple to get away with, and since the DB is used in a law office, any down time is big trouble for me!

Did something similar once and ended up with replicas that wanted nothing to do with the 'new' DB. It became apparent that the new copy was recognized as being somehow different, and no end of grief in errors like 'synchronization failed, there is no common point from which to begin' Compacting did this to me once too.

Oh well, time to try it on a single workstation, and keep my fingers crossed!


Thanks

Ray