If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below. |
|
|
Thread Tools | Display Modes |
#1
|
|||
|
|||
Query messed up by relationship change?
I'm not sure I can explain this clearly enough to get help, but I'm going to
try. I have a bunch of queries, and forms based on those queries which were working just fine. I have several front ends which access the same back end. Somehow, about five forms, based on different queries have stopped accepting new entries. Different versions of the front end have the same problems. I am fairly confident that I did not mess with the queries, so I assume that I somehow deleted or changed a key relationship. Is it the relationships that are given in the back end that matter, as I assume? Any wild guesses as to what I might have done? Thanks for any help you can give me, I realize that this is asking for a wild stab in the dark. |
#2
|
|||
|
|||
A related question: I have pretty much verified that the problem is in the
relationships of the back end, since switching a front-end over to linking to a back-up back end fixes the problem. Is there any way to copy a set of relationships from one database to another? Or do I have to sketch out all the relationships, and craft a repair? If I just switch to the backup, I'll lose a week's worth of data, and I'm really reluctant to do that. "r. howell" wrote: I'm not sure I can explain this clearly enough to get help, but I'm going to try. I have a bunch of queries, and forms based on those queries which were working just fine. I have several front ends which access the same back end. Somehow, about five forms, based on different queries have stopped accepting new entries. Different versions of the front end have the same problems. I am fairly confident that I did not mess with the queries, so I assume that I somehow deleted or changed a key relationship. Is it the relationships that are given in the back end that matter, as I assume? Any wild guesses as to what I might have done? Thanks for any help you can give me, I realize that this is asking for a wild stab in the dark. |
#3
|
|||
|
|||
to make use of the valid relationships in the backup database, without
losing current data, you can: make a copy of your backup backend database, and make a copy of your "live" backend database (after everyone is out of it for the day). then try the following, working ONLY with the COPIES you made. 1. delete all records from all tables in the backup db. 2. link in all the tables from the live db. 3. run append queries to copy all data from the linked live db tables into the backup db tables. note: this can be tricky. you have to append the data to all "parent" tables first, before appending data into "child" tables - otherwise, if referential integrity is enforced in your relationships, Access will not allow appending "orphan" child records. and remember to make sure you're working with the COPIES you made of the backup and live backend databases, not the "real" dbs. hth "r. howell" wrote in message ... A related question: I have pretty much verified that the problem is in the relationships of the back end, since switching a front-end over to linking to a back-up back end fixes the problem. Is there any way to copy a set of relationships from one database to another? Or do I have to sketch out all the relationships, and craft a repair? If I just switch to the backup, I'll lose a week's worth of data, and I'm really reluctant to do that. "r. howell" wrote: I'm not sure I can explain this clearly enough to get help, but I'm going to try. I have a bunch of queries, and forms based on those queries which were working just fine. I have several front ends which access the same back end. Somehow, about five forms, based on different queries have stopped accepting new entries. Different versions of the front end have the same problems. I am fairly confident that I did not mess with the queries, so I assume that I somehow deleted or changed a key relationship. Is it the relationships that are given in the back end that matter, as I assume? Any wild guesses as to what I might have done? Thanks for any help you can give me, I realize that this is asking for a wild stab in the dark. |
#4
|
|||
|
|||
Two hours later, I can say, THANK YOU, thank you, thank you. It worked. Now
I will be much more careful fussing with relationships in the future. It might have taken a very long time to figure out exactly what line I deleted, or added that messed the queries up, and in the meantime my prime users could not use the database. "tina" wrote: to make use of the valid relationships in the backup database, without losing current data, you can: make a copy of your backup backend database, and make a copy of your "live" backend database (after everyone is out of it for the day). then try the following, working ONLY with the COPIES you made. 1. delete all records from all tables in the backup db. 2. link in all the tables from the live db. 3. run append queries to copy all data from the linked live db tables into the backup db tables. note: this can be tricky. you have to append the data to all "parent" tables first, before appending data into "child" tables - otherwise, if referential integrity is enforced in your relationships, Access will not allow appending "orphan" child records. and remember to make sure you're working with the COPIES you made of the backup and live backend databases, not the "real" dbs. hth "r. howell" wrote in message ... A related question: I have pretty much verified that the problem is in the relationships of the back end, since switching a front-end over to linking to a back-up back end fixes the problem. Is there any way to copy a set of relationships from one database to another? Or do I have to sketch out all the relationships, and craft a repair? If I just switch to the backup, I'll lose a week's worth of data, and I'm really reluctant to do that. "r. howell" wrote: I'm not sure I can explain this clearly enough to get help, but I'm going to try. I have a bunch of queries, and forms based on those queries which were working just fine. I have several front ends which access the same back end. Somehow, about five forms, based on different queries have stopped accepting new entries. Different versions of the front end have the same problems. I am fairly confident that I did not mess with the queries, so I assume that I somehow deleted or changed a key relationship. Is it the relationships that are given in the back end that matter, as I assume? Any wild guesses as to what I might have done? Thanks for any help you can give me, I realize that this is asking for a wild stab in the dark. |
#5
|
|||
|
|||
you're welcome!
"r. howell" wrote in message ... Two hours later, I can say, THANK YOU, thank you, thank you. It worked. Now I will be much more careful fussing with relationships in the future. It might have taken a very long time to figure out exactly what line I deleted, or added that messed the queries up, and in the meantime my prime users could not use the database. "tina" wrote: to make use of the valid relationships in the backup database, without losing current data, you can: make a copy of your backup backend database, and make a copy of your "live" backend database (after everyone is out of it for the day). then try the following, working ONLY with the COPIES you made. 1. delete all records from all tables in the backup db. 2. link in all the tables from the live db. 3. run append queries to copy all data from the linked live db tables into the backup db tables. note: this can be tricky. you have to append the data to all "parent" tables first, before appending data into "child" tables - otherwise, if referential integrity is enforced in your relationships, Access will not allow appending "orphan" child records. and remember to make sure you're working with the COPIES you made of the backup and live backend databases, not the "real" dbs. hth "r. howell" wrote in message ... A related question: I have pretty much verified that the problem is in the relationships of the back end, since switching a front-end over to linking to a back-up back end fixes the problem. Is there any way to copy a set of relationships from one database to another? Or do I have to sketch out all the relationships, and craft a repair? If I just switch to the backup, I'll lose a week's worth of data, and I'm really reluctant to do that. "r. howell" wrote: I'm not sure I can explain this clearly enough to get help, but I'm going to try. I have a bunch of queries, and forms based on those queries which were working just fine. I have several front ends which access the same back end. Somehow, about five forms, based on different queries have stopped accepting new entries. Different versions of the front end have the same problems. I am fairly confident that I did not mess with the queries, so I assume that I somehow deleted or changed a key relationship. Is it the relationships that are given in the back end that matter, as I assume? Any wild guesses as to what I might have done? Thanks for any help you can give me, I realize that this is asking for a wild stab in the dark. |
Thread Tools | |
Display Modes | |
|
|
Similar Threads | ||||
Thread | Thread Starter | Forum | Replies | Last Post |
Help with a query...Have a 1 to many relationship need help | Scott Bridges | Running & Setting Up Queries | 5 | January 13th, 2005 11:39 PM |
Taher | Setting Up & Running Reports | 1 | August 31st, 2004 09:07 PM | |
Newbie? Do I use Report or Query | John Egan | New Users | 11 | June 28th, 2004 08:31 PM |
Change query for report, plus iif question | dw | Setting Up & Running Reports | 3 | June 1st, 2004 04:13 PM |