I've just upgraded to 4GL for Windows 4.11.WD1 and INET PC 5.01 and my app has stopped working. It worked
fine with 4GL 4.11.WC2P2 and INET 4.10.DC1. It also works fine with the new 4GL and the old INET. The server
is a constant: Online 5.00.UC3 running on a Sun.
The app is a mixed C and 4GL app that uses the Windows API to present a GUI to the user. The 4GL part creates
2 temp tables and a scroll cursor, fetches from the scroll cursor, closes and frees the cursor, and then drops
the 2 temp tables. When run with the new INET the DROP TABLE fails with error -314 (Table xxx currently in
use). Note that all cursors on the temp tables have been closed prior to the DROP TABLE.
Has anyone else run into this problem? And better yet: worked around it? We speculate that it has something
to do with the mechanism by which INET identifies the app that's connecting to it, ie, whether INET is using a
window handle from the app, the app's instance handle, or something else.
Any clues will be useful.
Thanks,
Dave Ellis