Trying to print a report when another user is using the table

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • mulchgirl
    New Member
    • Apr 2008
    • 27

    Trying to print a report when another user is using the table

    When we have one of our users is entering info into a table via a form and another user attempts to print a report based on the same table, they get the message "the databaase engine could not lock table "Freight" because it is already in use by another person or process". Is there a way around this?
  • NeoPa
    Recognized Expert Moderator MVP
    • Oct 2006
    • 32662

    #2
    Check your locking options in Tools / Options / Advanced.

    This needs to be considered for any / all relevant PCs.

    Comment

    • mulchgirl
      New Member
      • Apr 2008
      • 27

      #3
      Thanks for your help. I checked the advanced settings on both computers and they are both set to "Shared" and "No Locks." Would there be anything else I am missing?

      Comment

      • NeoPa
        Recognized Expert Moderator MVP
        • Oct 2006
        • 32662

        #4
        Nothing springs to mind.

        Are these set on all involved computers?

        Comment

        • mulchgirl
          New Member
          • Apr 2008
          • 27

          #5
          The database is on our server - all computers can access the dbase through shortcuts. I checked the original and it also is "Shared" and "No Locks." Could it just be that when someone is entering info into a table, that you can't run reports off that table?

          Comment

          • mulchgirl
            New Member
            • Apr 2008
            • 27

            #6
            I was digging a little deeper - I can run the query that the report is based on while our other user is using the dbase. But as soon as I try and run the report, I get that error message again - could it be something in the reports properties?

            Comment

            • mulchgirl
              New Member
              • Apr 2008
              • 27

              #7
              Woo Hoo! I checked the report's properties and found a "Record Locks" and saw that it was set to "All Records." So I changed it to "No Locks" and it now works - thank you so much for your wisdom!!!!!

              Comment

              • NeoPa
                Recognized Expert Moderator MVP
                • Oct 2006
                • 32662

                #8
                It seems like your own determination and searching got you over this one my girl. Well done :)

                Comment

                Working...