softwarescience
Programmer
I ask a user to select a file from the "A:" drive.
Then they exit the application.
When they restart the application there is no floppy in the "A:" drive and when I call "Connection.Open" (ADO 2.6) VB6 always checks the A drive (and displays the 'cannot read drive 'A' dialogue)BEFORE actually opening the connection object.
I know this can be resolved by placing 'ChDrive "C:"' at the start of the exe BUT I would like to know if anyone has any information as to why VB checks the current drive when opening a ADO connection.
If anyone has seen this before or found a reason for it I would love to know, as it seems a completely illogical feature of the ADO open method.
Many thanks
Then they exit the application.
When they restart the application there is no floppy in the "A:" drive and when I call "Connection.Open" (ADO 2.6) VB6 always checks the A drive (and displays the 'cannot read drive 'A' dialogue)BEFORE actually opening the connection object.
I know this can be resolved by placing 'ChDrive "C:"' at the start of the exe BUT I would like to know if anyone has any information as to why VB checks the current drive when opening a ADO connection.
If anyone has seen this before or found a reason for it I would love to know, as it seems a completely illogical feature of the ADO open method.
Many thanks
