I hope I describe this correctly. I have tables called File, Client and Accident. Each has a a unique ID Field. One file has one client and one accident only (though one client can have many Files or one Accident many Files). In the File Table is a field for the client ID and another for the accident. This was originally part of a database set up in 2003 using version 5.
I am now updating to version 10.5. In the last seven years about 4000 new records have been set up in the File table, and close to that in the client and accident. There were about 5000 records already in the tables from a previous database program (the much loved Q&A). Now the problem. The person(s) in my office who sets up new cases have had a tendency in the last few years to begin the process, create the Client record, go to lunch or something like that, and then come back and end up recreating the Client Record, and finish the process. There could be five client records, each with their own ID, and one File with one of those IDs. In the search client dialog box, you would see one client multiple times, and have no idea but by trial and error to figure out which one was associated to a File.
Now that I have spent my time (and while, as clear as this is, I am not a programmer, I love this stuff) redesigning the application I want to go back and delete the extraneous client records -leaving only those who have a File record associated with it. How do I design this operation? It must mark Client records that are not associated with a File records. The key is the Client ID.
This is not going to make or break the fact that after this weekend we will be using version 10.5 in our office. It is perplexing me -any thoughts or suggestions would be appreciated.
I am now updating to version 10.5. In the last seven years about 4000 new records have been set up in the File table, and close to that in the client and accident. There were about 5000 records already in the tables from a previous database program (the much loved Q&A). Now the problem. The person(s) in my office who sets up new cases have had a tendency in the last few years to begin the process, create the Client record, go to lunch or something like that, and then come back and end up recreating the Client Record, and finish the process. There could be five client records, each with their own ID, and one File with one of those IDs. In the search client dialog box, you would see one client multiple times, and have no idea but by trial and error to figure out which one was associated to a File.
Now that I have spent my time (and while, as clear as this is, I am not a programmer, I love this stuff) redesigning the application I want to go back and delete the extraneous client records -leaving only those who have a File record associated with it. How do I design this operation? It must mark Client records that are not associated with a File records. The key is the Client ID.
This is not going to make or break the fact that after this weekend we will be using version 10.5 in our office. It is perplexing me -any thoughts or suggestions would be appreciated.
Comment