Results 1 to 9 of 9

Thread: ADO giving me problems

  1. #1

    Thread Starter
    Addicted Member
    Join Date
    Jan 2000
    Location
    Peterborough, Cambs, England
    Posts
    176

    Post

    Hi

    I have almost competed an application for database access.

    The program works perfectly on my computer, but if I run it on an other computer I get the following error...

    The Microsoft Jet database engine cannot open the file 'E:\shared\procedure.mdb'. It is already opened exclusively by another user, or you need permission to view its data.

    The database isn't open by another user exclusively or otherwise. There are no permissions set for it and the other computers have full read/write access to the database. The database doesn't have a password or anything like that.

    The program was made with VB6 Pro with SP3 installed.


    I would appreciate any help given.

    Thanks!

  2. #2
    Lively Member
    Join Date
    May 1999
    Location
    Vancouver, BC, Canada
    Posts
    84

    Post

    Is E:\shared\procedure.mdb a hard disk or a CD?

    I use a CD burner to move large apps to my clients' workstations without a setup program. When I copy files from a burned CD, they are all Read Only and unless I change the file properties, I get the same error.

  3. #3

    Thread Starter
    Addicted Member
    Join Date
    Jan 2000
    Location
    Peterborough, Cambs, England
    Posts
    176

    Post

    Thanks for replying.

    My database is not read-only.

    The E:\shared... etc. is a net work drive.

    But the same thing happens if I copy the database on to the C: drive and point the ADO control at it.

    The error appears at a point in my program which refreshes it after giving it an SQL string...

    adoProcedure.RecordSource = "SELECT id, desc, qty FROM procedures ORDER BY desc"
    adoProcedure.CommandType = AdCmdText
    adoProcedure.Refresh

    The error occurs on the last line.

  4. #4
    Guru Clunietp's Avatar
    Join Date
    Oct 1999
    Location
    USA
    Posts
    1,844

    Post

    Is your database read only?

    Also check out this link: http://support.microsoft.com/support...G=ENG&SA=ALLKB

  5. #5
    Guru Clunietp's Avatar
    Join Date
    Oct 1999
    Location
    USA
    Posts
    1,844

    Post

    You said that it was a network drive....does the user have WRITE permission on that drive? Write permission is needed to create the locking file (ldb file), and if it can't be created, you will get that error....check with your server admin

  6. #6

    Thread Starter
    Addicted Member
    Join Date
    Jan 2000
    Location
    Peterborough, Cambs, England
    Posts
    176

    Post

    Hi Clunietp,

    I am the network administrator, and all the computers on the network have full read and write permissions to that particualr drive.

    Thanks fro replying though.

    Any other possible solutions?

  7. #7
    Member
    Join Date
    Nov 1999
    Posts
    63

    Post

    Paul,

    Is it possible that somewhere else in the application there was a use exclusive connection established that was not closed?

    Do you by chance have user level security on the database through a workgroup file (*.mdw)?

    Gerald

  8. #8
    New Member
    Join Date
    Jan 2000
    Location
    Oxfordshire
    Posts
    13

    Post

    Just a thought, try setting the "Cursor Type" as "adOpenKeyset" and the "LockType" as "adLockOptimistic" it should allow multi user access!

  9. #9
    Guest

    Post

    USE DAO INSTEAD

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  



Click Here to Expand Forum to Full Width