Results 1 to 2 of 2
2006-03-03, 15:02 #1
- Join Date
- May 2002
- Toronto, Ontario, Canada
- Thanked 0 Times in 0 Posts
Data changed to Binary data type?? (2003 SP2)
I'm seeing the weirdest issues come up during this Access 97 to 2003 conversion... An automated process that worked fine in 97 is not working in 2003... I've traced it back to some Make Table queries... The data contains a "Maturity" field... In the old database when I ran the make table query, the resulting table had the Maturity as Text data type... For some unknown reason the resulting table now has the Maturity data as Binary data type... ???... The even more bizarre thing to me is that Binary is not even one of the choices of data types in the drop down list for a field when designing a table.... ???... I'm working on adding CStr() all over the place and hoping that fixes my problem... I am just confused as to why it's happening and wanted to see if anyone else has come across this before... Now I'm concerned that it is happening in other databases used in the department and not being noticed... It is certainly not something I would have tested for... <img src=/S/confused.gif border=0 alt=confused width=15 height=20>
2006-03-03, 15:15 #2
- Join Date
- Mar 2002
- Thanked 30 Times in 30 Posts
Re: Data changed to Binary data type?? (2003 SP2)
Although Binary is not available in the Access interface, it is one of the data types supported by the Jet Database Engine, mostly for compatibility with other database systems.
Whenever possible, you should avoid using make table queries - the defaults for field types are not ideal (Text:255 for text fields, Double Precision for all number fields). Instead, create a table with the correct fields and field sizes, and use a combination of a delete query to remove existing records and an append query to add new records.