ODBC and ACCESS (OpenInsight 32-bit Specific)
At 01 SEP 2005 11:43:46AM Ray Chan wrote:
I'm doing an evaluation of the ODBC. Running OI7.1.1 and latest version of RTI's ODBC. Several questions to my fellow developers out there:
1) From Access, I can get the ODBC to work and see the LH files in our application. However, for a couple of files, when we select them for "importing", it just HANGS in ACCESS. We let it sit for 90 minutes to make sure that we were not impatience.
We have deleted out the "G" dictionary type and all Varchar set to 255.
On the otherhand, I have been successful in "importing" our ZIP Code file into Access (about 43,000 entries). Whereas our test Patient table, which we have not had any success has about 5,000 entries, but the dictionary structure contains many symbolics.
Is the ODBC affected by Symbolics? Or Multi-value fields?
2) How does the ODBC handle Multiple Value items?
3) When I initially started playing with the ODBC, I would get a message that the "QDICT table is not available." To get around this message, I create the "QDICT" table. After which I was able to proceed. After some modest success with the ODBC, I decide to delete the "QDICT" table. After doing this, I could still see the OI tables. Then I decide to test something. I copied the Sysprog DBT file over to my APPLICATION.DBT. After doing this, the missing "QDICT" message resurrected itself.
Why is this "QDICT" message coming up? Also, what's the relationship between the ODBC and the DBT file?
4) The ODBC driver does not work in a split environtment (Develop/Runtime). Does anyone know if this might be addressed in the future?
5) At present the ODBC is read-only, how hard would it be to make it read/write? (Not by me of course)
Any comments/suggestions would be apprecitated. Again, many thanks,
Ray Chan
P.S. I posted this on the other side as well.