When using the Microsoft ADO interface to access files managed by DB/C FS 2, it seems that the column description from the DBD file becomes the column name. How can we get around this?
ADO uses ODBC to access information in ODBC databases such as DB/C FS. The ODBC API has grown over the years and is now quite complicated. Many functions were added in ODBC 2.x and ODBC 3.x. Some of the capabilities of the newer ODBC functions overlap the capabilities of older functions. The DB/C FS ODBC driver that comes with DB/C FS 2.2 is ODBC 3.x compliant. There are several ODBC functions that client software can call to retrieve the name, label, remarks and other information about a column. We have tried to adhere to the Microsoft documentation for those ODBC functions that DB/C FS uses. Unfortunately, the documentation having to do with column information isn’t very clear. It appears that ADO uses certain ODBC functions in a way that causes the column description to become the column name. This problem is resolved in DB/C FS 3.
Related Questions
- We do not actually use Microsoft Exchange, but still have PST files generated from POP3 and SMTP servers and email. Will .PST Attender work with these types of PST files?
- Does HPV Web/Server support loading MPP Files from Microsoft Project Server?
- Is there a website that can convert Microsoft Works files to Word format?
