GREAT!
John,
YES that worked. The new table is in place and all the subforms are pulling the correct information.
Thank you very much.
Bill
MN
From: MS_Access_Professionals@yahoogroups.com [mailto:MS_Access_Professionals@yahoogroups.com]
Sent: Friday, July 18, 2014 12:50 PM
To: MS_Access_Professionals@yahoogroups.com
Subject: Re: [MS_AccessPros] Database error
Bill-
Copy the table to the clipboard, then paste Structure only. Delete the offending index in the new table before you try to load any data. Then build an Append (INSERT INTO) query to copy all the rows from the broken table to the new one. If that goes OK, then rebuild the index in the new table. Finally, delete the broken table, rename the new table and rebuild the relationships, then compact and repair to permanently delete the broken table.
John Viescas, Author
Microsoft Access 2010 Inside Out
Microsoft Access 2007 Inside Out
Microsoft Access 2003 Inside Out
Building Microsoft Access Applications
SQL Queries for Mere Mortals
(Paris, France)
On Jul 18, 2014, at 1:14 PM, 'Bill Singer' Bill.Singer@at-group.net [MS_Access_Professionals] <MS_Access_Professionals@yahoogroups.com> wrote:
John,
I went to the back end and did the copy and Paste of the table. Yes it has the same error. I can only sort through 301 records.
Is there a way I can import the records into a new table one record at a time. I am thinking that would maybe fix the index. I know I can do it I just cant remember how. I will do some research over the weekend.
I have not tried Bill Mosca's suggestion of importing the whole data base one table at a time. I do not have that much time right now.
Thanks,
Bill
From: MS_Access_Professionals@yahoogroups.com [mailto:MS_Access_Professionals@yahoogroups.com]
Sent: Wednesday, July 16, 2014 12:17 PM
To: MS_Access_Professionals@yahoogroups.com
Subject: Re: [MS_AccessPros] Database error
Bill-
It sounds like the index for ConCusID is corrupted. In the back end, copy the table to the clipboard and paste as a new table. See if the new table has the same problem. If not, then delete the old table and rename the new one. You'll probably also have to rebuild any relationships.
John Viescas, Author
Microsoft Access 2010 Inside Out
Microsoft Access 2007 Inside Out
Microsoft Access 2003 Inside Out
Building Microsoft Access Applications
SQL Queries for Mere Mortals
(Paris, France)
On Jul 16, 2014, at 12:56 PM, 'Bill Singer' Bill.Singer@at-group.net [MS_Access_Professionals] <MS_Access_Professionals@yahoogroups.com> wrote:
More information on this error. My customer contact table had 3700 records.
When I sort the table by the ID number it still shows 3700 records. When I sort by name I get 3700 records. When I sort by the "ConCusID" which is the child field that connects to the CustomeID number in the customer table the sort only shows 320 records. I scroll down and only 320 show. When I change my sort, I get back to 3700. When I try to filter my contact records for any contacts for Customer ID 331, I get that same database error listed below.
It does not help either when I bang my head against the desk.
Any thought on reasons or fixes?
Thanks,
Bill
From: MS_Access_Professionals@yahoogroups.com [mailto:MS_Access_Professionals@yahoogroups.com]
Sent: Wednesday, July 16, 2014 11:35 AM
To: MS_Access_Professionals@yahoogroups.com
Subject: [MS_AccessPros] Database error
I recently updated to Access 2013 from Access 2007.On the FE Database I have a main form (Customers) with a subform (Customer Contacts). The forms are linked by the parent/child association via the ID number on the Customer form.
As I input work through the Customers all the contacts change just like they are supposed to… except I have one or two records that for some reason do not work. When I go to customer 270 I am getting all the customer contacts for customer 270, but when I go to customer 331 I get the contacts for 3482. When I go to customer 3482 the contacts for 3482 show up.
When I go to contact 330 and go forward one record to 331 (which is the problem record) I get this message. "Cannot open database". It may not be a database that your application recogonizes, or the file may be corrupt.
I did a compact repair on the front end and that did not change anything. I tried a back up older database and that did not change anything. I am guessing it is in the back end. The back up and repair did change anything except I got a lot of records with ########### in them. I do not know what that means.
Any thoughts on why I would have problems with just one record (Customer with ID number 331)?
Any thoughts on what I should do?
Could this be caused by a person editing a record and then going home at night before the record is saved?
Thanks,
Bill
MN
Posted by: John Viescas <johnv@msn.com>
| Reply via web post | • | Reply to sender | • | Reply to group | • | Start a New Topic | • | Messages in this topic (8) |
Tidak ada komentar:
Posting Komentar