jeebusmn
04-18-2007, 06:01 AM
I would appreciate any help that anyone has on my problem. Most of what I understand about it is from playing with it and carry over from Excel.
Here is my problem. There is a program Petrodocs that we are using that creates a odbc database. The program creates two separate tables (loops, and instruments). I am using Access to manipulate the database because Petrodocs makes Windows Vista seem like a relatively bug free platform. Every instrument in the instrument table is tied to a loop in the loop table. When I open up the instrument table in Access, there is a column which contains which loop it is linked to in the format of "1004H". My guess is that the program doesn't link the two items but just uses the "1004H" to find the associated loop in the loop table. The "1004H" is a loop identifier but the format in the loop table is Column A, "H", Column B "1004". This makes it difficult to create a quick and easy relationship.
I have been working around this in half-ass sort of way by exporting the loop and instrument tables to Excel and there concatenating and parsing the strings (1004H) so that I could make a direct comparison and link the information together. I have then been importing the Excel file into Access and linking my Access tables to the Excel tables and creating the proper relationships. This solves my problem for about 2/3s of my entries in my Instrument table. I think it is not working for all of them due to some parsing issues. Even if I work out the bugs this is not how I want to be doing it because if an item is changed in either loop or instrument tables, I have to manually copy and paste them into the Excel tables to create the proper relationship between the two Access tables, LOOP and INSTRUMENTS.
So, how would you solve this problem?
Here is my problem. There is a program Petrodocs that we are using that creates a odbc database. The program creates two separate tables (loops, and instruments). I am using Access to manipulate the database because Petrodocs makes Windows Vista seem like a relatively bug free platform. Every instrument in the instrument table is tied to a loop in the loop table. When I open up the instrument table in Access, there is a column which contains which loop it is linked to in the format of "1004H". My guess is that the program doesn't link the two items but just uses the "1004H" to find the associated loop in the loop table. The "1004H" is a loop identifier but the format in the loop table is Column A, "H", Column B "1004". This makes it difficult to create a quick and easy relationship.
I have been working around this in half-ass sort of way by exporting the loop and instrument tables to Excel and there concatenating and parsing the strings (1004H) so that I could make a direct comparison and link the information together. I have then been importing the Excel file into Access and linking my Access tables to the Excel tables and creating the proper relationships. This solves my problem for about 2/3s of my entries in my Instrument table. I think it is not working for all of them due to some parsing issues. Even if I work out the bugs this is not how I want to be doing it because if an item is changed in either loop or instrument tables, I have to manually copy and paste them into the Excel tables to create the proper relationship between the two Access tables, LOOP and INSTRUMENTS.
So, how would you solve this problem?