Login ProductsSalesSupportDownloadsAbout |
Home » Technical Support » ElevateDB Technical Support » Support Forums » ElevateDB General » View Thread |
Messages 1 to 2 of 2 total |
DBISAM / ElevateDB units precedence |
Sat, Apr 7 2007 9:46 AM | Permanent Link |
Roy Lambert NLH Associates Team Elevate | Tim
I think we're going to need some advice about ElevateDB and DBISAM crossovers for those (hopefully) rare occasions where there is a problem. I've just encountered my second one (lpPessimistic) and in this case it seems to be solved by moving edbcomps before DBISAMTb, DBISAMCn, lt worries me because I don't know if there are deeper implications. The last one was Session and I'm not certain about the positioning for the stuff but I think it was the same. Roy Lambert |
Mon, Apr 9 2007 8:37 PM | Permanent Link |
Tim Young [Elevate Software] Elevate Software, Inc. timyoung@elevatesoft.com | Roy,
<< I think we're going to need some advice about ElevateDB and DBISAM crossovers for those (hopefully) rare occasions where there is a problem. I've just encountered my second one (lpPessimistic) and in this case it seems to be solved by moving edbcomps before DBISAMTb, DBISAMCn, lt worries me because I don't know if there are deeper implications. The last one was Session and I'm not certain about the positioning for the stuff but I think it was the same. >> Just preface the references with the proper unit (dbisamtb or edbcomps). That way you don't need to rely on the unit reference ordering in the USES clause. -- Tim Young Elevate Software www.elevatesoft.com |
This web page was last updated on Tuesday, May 7, 2024 at 02:40 AM | Privacy PolicySite Map © 2024 Elevate Software, Inc. All Rights Reserved Questions or comments ? E-mail us at info@elevatesoft.com |