Datasheet View Subforms - Not Allowing Data Entry

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • CCHDGeek
    New Member
    • Oct 2007
    • 23

    Datasheet View Subforms - Not Allowing Data Entry

    I have a subform that is searched according to a field value on the main form.

    The subform has mutiple pages and each page has a subform based off a query. Today when I logged into the main form, none of the subforms that in are Datasheet view are allowing data entry. In fact, none of the rows are even visible. All I can see is the column title row for each datasheet. What does this mean? Are my queries not setup correctly? Is it an issue with allowing data entry?

    This has happened before, and usually if I recreate the query, it fixes the problem. I would like to not have to do this though.

    Any help would be fantastic.

    Thank you.
  • PianoMan64
    Recognized Expert Contributor
    • Jan 2008
    • 374

    #2
    Are you using a MS Access Backend or some other backend like MS SQL or Oracle?

    Comment

    • CCHDGeek
      New Member
      • Oct 2007
      • 23

      #3
      Yes, I am using an Access Backend.

      Comment

      • PianoMan64
        Recognized Expert Contributor
        • Jan 2008
        • 374

        #4
        Originally posted by CCHDGeek
        Yes, I am using an Access Backend.
        Is it split or are you running it as one file?

        Comment

        • CCHDGeek
          New Member
          • Oct 2007
          • 23

          #5
          It is split and runs across a network.

          Comment

          • CCHDGeek
            New Member
            • Oct 2007
            • 23

            #6
            I am still having issues w/this problem. It seems now that while the database is in use on another computer, it does not work correctly on any others. On some computers, the subform is disappearing altogether. Is this a problem w/the way my backend is setup?

            Thanks.

            Comment

            • missinglinq
              Recognized Expert Specialist
              • Nov 2006
              • 3533

              #7
              Originally posted by CCHDGeek
              It is split and runs across a network.
              Does this mean the back end is on a server on the network and the front ends are on each user's PC? Or are the users sharing a front end that's also on the network? Sharing a front end can cause this type of problem as well as many others, including repeated corruption.

              Linq ;0)>

              Comment

              • CCHDGeek
                New Member
                • Oct 2007
                • 23

                #8
                The backend is saved on a shared drive on the network. Each user has an individual front in that is saved on their personal computer.

                I was forced by my employer to build a database for our team, and it's been a difficult road - figuring out everything. WIthout this board, I'd be totally lost.


                Originally posted by missinglinq
                Does this mean the back end is on a server on the network and the front ends are on each user's PC? Or are the users sharing a front end that's also on the network? Sharing a front end can cause this type of problem as well as many others, including repeated corruption.

                Linq ;0)>

                Comment

                Working...