[RBASE-L] - Re: SATTACH, QUALKEY, COLUMN Type Mismatch?

[Emmitt Dove]

What happens if you connect to the production database, sconnect the ad_hoc database and perform the insert from the sattached table to the permanent table?

I'm with Albert in that I would spell out the columns in the receiving table, but the select * from should work fine.

Another method would be to try APPEND.

I'm sure someone knows something about this one ...
 
I have a PRODUCTION database and an AD_HOC database that contain some tables which are exactly identical.  I use the AD_HOC to prepare (LOAD, parse, INSERT, Etc) data that we receive as flat-file ASCII before I LOAD it into the PRODUCTION database.  So, when I have a connection to the AD_HOC and SCONNECT to the PRODUCTION database therefrom, I SATTACH one of the identical tables, using an alias, and choosing SSN (defined exactly the same in both tables) as the column-set to uniquely identify the SATTACHed table.  All this is fine.  However, when I attempt :
 
INSERT INTO ALIAS_TABLE_A (*) SELECT * FROM TABLE_A WHERE ...    -- WHERE-clause shouldn't be a factor as the SELECT component executes fine
 
I get this in a message box :
 
"[RBTI][R:BASE ODBC Driver][PRODUCTION]-ERROR- Column SSN must be a valid TEXT (122)"
 
Any ideas?
 
 
Thanks,
Steve in Memphis

Emmitt Dove
Manager, DairyPak Business Systems
Blue Ridge Paper Products, Inc.
40 Lindeman Drive
Trumbull, CT  06611
(203) 673-2231
[EMAIL PROTECTED]
[EMAIL PROTECTED]