R
RockyMu
I have an Access Project which has several combo box fields that have a
lookup table. In SQL server, I have a Data Transformation (DTS) routine to
convert selected records, from the same table used in Access, to delimited
text. However, when I look at the fields in SQL Server that were combo boxes
in Access, the data has gone through some conversion process and is different
(e.g. OCC024000 is 1970 or something like that.) Of course, in SQL Server the
data is viewed as a simple text box. I tried this in Access and the same
thing happend. That is, if I put data into the form combo box, selecting data
from the drop down lookup list, and then later view the same data in table
format where the fields are defined as simple text boxes, the data has been
changed just as in SQL Server. Why is data, which is entered into a form or
table using a combo box lookup, not compatible with a view that uses a simple
text box for the same fields??
lookup table. In SQL server, I have a Data Transformation (DTS) routine to
convert selected records, from the same table used in Access, to delimited
text. However, when I look at the fields in SQL Server that were combo boxes
in Access, the data has gone through some conversion process and is different
(e.g. OCC024000 is 1970 or something like that.) Of course, in SQL Server the
data is viewed as a simple text box. I tried this in Access and the same
thing happend. That is, if I put data into the form combo box, selecting data
from the drop down lookup list, and then later view the same data in table
format where the fields are defined as simple text boxes, the data has been
changed just as in SQL Server. Why is data, which is entered into a form or
table using a combo box lookup, not compatible with a view that uses a simple
text box for the same fields??