Never mind! 



I am going a little nuts.  There was a second common column in the local 

table that I must have looked at 3 times before and it did not register as 

being common to table 2.   Altough the column name was the same, it 

would not hold the same values (AuditUser, holding the last user to modify 

the record)  Man, I cannot believe how many times I listed tables to review 

column names! 



Thanks any way. 



-Bob 





----- Original Message ----- 
From: "ttc inc" <[email protected]> 
To: "RBASE-L Mailing List" <[email protected]> 
Sent: Monday, December 20, 2010 2:37:44 PM 
Subject: [RBASE-L] - ODBC and local slave table 







----- Original Message ----- 
From: "ttc inc" <[email protected]> 
To: "RBASE-L Mailing List" <[email protected]> 
Sent: Monday, December 20, 2010 2:37:44 PM 
Subject: [RBASE-L] - ODBC and local slave table 




I have a form that has three tables.  The main table is an ODBC connected 

table, then a second ODBC table with the third slave table local to 
the database. 



I.E. 



ODBC Table A 

| 

ODBC Table B 

| 

Local Table C 



All three tables have only one common column "SerialNo" of the same data type. 



When I edit data with the form, tables A & B populate, but C does not.  If I 
project 

temporary local tables from A & B and use them in the form instead of the ODBC 

versions, all three tables populate when using the form. 



At first look, it seems that a form does not like to mix ODBC tables with local 
tables. 



Can any one please confirm this or offer input.  



(Using the projected local tables is not an option for the application.  I have 
confirmed 

that all three tables have a common column of the same name and data type) 



Thanks, 

-Bob 













Reply via email to