Missing data???

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • ConfusedMay
    New Member
    • Apr 2007
    • 57

    Missing data???

    Hi,

    I have a weird problem. I have an access database (in access 2003) with a link table from SQL called log with total records 20290. The problem is some computers show the whole record on the database, some don't. It only shows 20212 records. How is it possible since they're sharing the same database? how to fix this problem? Please help !!!!
  • puppydogbuddy
    Recognized Expert Top Contributor
    • May 2007
    • 1923

    #2
    Originally posted by ConfusedMay
    Hi,

    I have a weird problem. I have an access database (in access 2003) with a link table from SQL called log with total records 20290. The problem is some computers show the whole record on the database, some don't. It only shows 20212 records. How is it possible since they're sharing the same database? how to fix this problem? Please help !!!!
    Hi May,

    This advice is from post#16 of the following link. Hope it helps.


    --------------------------------------------------------------------------------

    You could try a Count query to verify that the records are available
    through the link or not.

    SELECT Count(*) as TotalRecords FROM myTable

    If this record count matched the record count on SQL Server, then it is
    not the link, but some limit in what you are viewing the data from (see
    David's post).

    If the Count does not match the SQL count (and I assume matches the
    count of your other viewing method) then something could be whacky with
    the link. Have you tried deleting and recreating the link to see if that
    makes a difference?

    Comment

    • ConfusedMay
      New Member
      • Apr 2007
      • 57

      #3
      Originally posted by puppydogbuddy
      Hi May,

      This advice is from post#16 of the following link. Hope it helps.


      --------------------------------------------------------------------------------

      You could try a Count query to verify that the records are available
      through the link or not.

      SELECT Count(*) as TotalRecords FROM myTable

      If this record count matched the record count on SQL Server, then it is
      not the link, but some limit in what you are viewing the data from (see
      David's post).

      If the Count does not match the SQL count (and I assume matches the
      count of your other viewing method) then something could be whacky with
      the link. Have you tried deleting and recreating the link to see if that
      makes a difference?
      Thanks for the reply. I did delete the link to that specific computer and relink it again, but the records still 20212. I can't open the table through the database it gave me an error saying "odbc call failed", but when I tried creating the query for the count, it gave me the records still 20212. The records should've been 20290. I updated the MDAC. Should I reinstall access 2003?

      Comment

      • puppydogbuddy
        Recognized Expert Top Contributor
        • May 2007
        • 1923

        #4
        Originally posted by ConfusedMay
        Thanks for the reply. I did delete the link to that specific computer and relink it again, but the records still 20212. I can't open the table through the database it gave me an error saying "odbc call failed", but when I tried creating the query for the count, it gave me the records still 20212. The records should've been 20290. I updated the MDAC. Should I reinstall access 2003?
        May,

        I would not reinstall Access 2003 just yet. Next I would check the max records property setting for the Access query that you used to obtain the record count on the linked table and verify that is >= to the server count. To check the max records property, place the query in design view, right click in the table area, but not on a table. On the shortcut menu, select properties, then page down to max records. The following link explains more detail and has a function to test how max records is operating when nothing has been set for that property.

        Comment

        • puppydogbuddy
          Recognized Expert Top Contributor
          • May 2007
          • 1923

          #5
          May,
          I found this on one of the public forums. Hope it helps.

          Record Counts in SQL Server Table
          Reply from Bryan Schoen on 4/5/2005 5:49:00 PM

          I have found that you can not rely 100% on the record counts that shows up
          in EM under the table properties. The counts that are displayed there come
          from the sysindexes table.

          Run the command DBCC UPDATEUSAGE to correct this problem. Look in BOL for the syntax.

          Comment

          • ConfusedMay
            New Member
            • Apr 2007
            • 57

            #6
            Originally posted by puppydogbuddy
            May,
            I found this on one of the public forums. Hope it helps.

            Record Counts in SQL Server Table
            Reply from Bryan Schoen on 4/5/2005 5:49:00 PM

            I have found that you can not rely 100% on the record counts that shows up
            in EM under the table properties. The counts that are displayed there come
            from the sysindexes table.

            Run the command DBCC UPDATEUSAGE to correct this problem. Look in BOL for the syntax.
            I found out what's going on. There's an error on the ms access driver on that specific computer. What I need to do is recreate the ms access driver and that's solved the problem.

            Comment

            • puppydogbuddy
              Recognized Expert Top Contributor
              • May 2007
              • 1923

              #7
              Originally posted by ConfusedMay
              I found out what's going on. There's an error on the ms access driver on that specific computer. What I need to do is recreate the ms access driver and that's solved the problem.
              May,
              Glad you got it resolved. Thanks for posting back and letting us know what the final resolution was.

              Comment

              Working...