Login ProductsSalesSupportDownloadsAbout |
Home » Technical Support » DBISAM Technical Support » Support Forums » DBISAM Client/Server » View Thread |
Messages 1 to 2 of 2 total |
DBISAM closed dataset problem under IW. |
Wed, Nov 11 2009 11:49 PM | Permanent Link |
"John Postnikoff" | I have a D7- DBISAM application running under IntraWeb (IW) and two
different D7 client programs that access the same database tables. It works great on two networks. When I try to run the IW application on another customer's network I get a ''cannot perform this operation on a closed dataset" error , thus the app is not able to access the tables when the application fires up. The applications does seem to start OK otherwise but does not display data. Yet it works fine when moved to another other system without changes as a server on a different network, and the D7 client applications work fine remotely. Any ideas on what to look for? I made all DB and application settings identical, including ports for forwarding and local IP addresses. I can access the tables with the DBSYS utility from a remote location. Could there be a server configuration file I need to install, edit or make sure it is in a certain path? |
Fri, Nov 13 2009 12:45 PM | Permanent Link |
Tim Young [Elevate Software] Elevate Software, Inc. timyoung@elevatesoft.com | John,
<< I have a D7- DBISAM application running under IntraWeb (IW) and two different D7 client programs that access the same database tables. It works great on two networks. When I try to run the IW application on another customer's network I get a ''cannot perform this operation on a closed dataset" error , thus the app is not able to access the tables when the application fires up. The applications does seem to start OK otherwise but does not display data. Yet it works fine when moved to another other system without changes as a server on a different network, and the D7 client applications work fine remotely. Any ideas on what to look for? >> This type of issue is almost always a session/threading issue with how sessions are used/reused within IW. What normally happens is that one thread steps on another, or one thread re-uses another session and gets it, or other components used within it, in a state that it doesn't expect. -- Tim Young Elevate Software www.elevatesoft.com |
This web page was last updated on Thursday, March 28, 2024 at 06:05 PM | Privacy PolicySite Map © 2024 Elevate Software, Inc. All Rights Reserved Questions or comments ? E-mail us at info@elevatesoft.com |