Discussion Locked

NT 4.0 16-bit support

0 helpful
1 reply
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

Enterprise Environment, Win9X, WinNT and Win2K client platforms. Over 9,000 users.

Support:

different IS teams for each department. Therefore different profiles are being installed, and different default profiles are being installed on various WinNT 4.0 desktops.

Issue:

16-bit ODBC and Win 16 support for some desktops have caused 16 apps to malfunction. we've located the issue as the 16 bit profiles aren't visible in the registry, and 16-bit ODBC ADM can't manage the proper DLLsbecause the 16-bit ODBC ADM only sees the 32-bit DLLs.

Question:

No matter how many times I create/recreate a profile, the prompt to ask me to migrate 16-bit support doesn't appear prior to the logon prompt. How do I resolve this issue? I need to be able to migrate 16-bit apps over to a profile that supports the 16-bit ODBC ADM; so that the 16-bit ODBC ADM also sees 16-bit ODBC instead of just 32-bit ODBC DLLs. Please send all responses to AnthonyBernardino@Engineer.com.

1 reply

by ong_matthew

If you need to access databases using the newer 32-bit ODBC drivers from a 16-bit application, you cannot do it directly. You will need to take the database access portion out of the 16-bit application. Build a brand new 32-bit application that willperform the database access. Then you can re-code your 16-bit application to use interprocess communication such as Sockets, DDE, and OLE
Automation in order to transfer data to and from new 32-bit application.
As it might turn out to be too muchwork, perform the above steps only if you have huge 16-bit application and data access is only a small part of it. If you have a smaller 16-bit application, it is best to reprogram and rebuild the application with the 32-bit version of Visual C++.The 16-bit SQL Server ODBC driver, which is included with SQL Server 6.5 can be used against SQL Server 7.0, although you will have some limitations, such not being able to use the new SQL 7.0 data types.

This discussion is closed to new replies.