Login ProductsSalesSupportDownloadsAbout |
Home » Technical Support » DBISAM Technical Support » Support Forums » DBISAM General » View Thread |
Messages 1 to 2 of 2 total |
Changing the extension of .blb files: In a backward compatible way ? |
Fri, Apr 11 2008 8:03 PM | Permanent Link |
Sam Jones | We are looking to change the extension of the blb files to our own, custom file extension.
The problem is that we use both client server and direct access, and multiple direct access, and and and and (lots of ands). So we can't just change the global property in DBISAM and be done. It is much messier than that. So a question came up, and I thought I would ask here: Is there a way for DBISAM to be 'flexible' in this regard ? E.g. We might set a DBISAM property to make the extension .memogidget When creating a new db (which our app does a lot), DBISAM would name blb files: .memogidget When connecting to a new db, DBISAM would look for .memogidget blb files, and use them if there. But if NOT there, would use .blb Could this be part of DBISAM? In this way, we could move to a new extension in a backward compatible way. Thanks! |
Mon, Apr 14 2008 3:29 PM | Permanent Link |
Tim Young [Elevate Software] Elevate Software, Inc. timyoung@elevatesoft.com | Sam,
<< Could this be part of DBISAM? >> Well, anything is possible, but I can't make any promises in this regard. I'd have to look into this further before I could comment on the feasibility of such an idea. I will see what I can do for the next DBISAM minor release. -- Tim Young Elevate Software www.elevatesoft.com |
This web page was last updated on Thursday, March 28, 2024 at 08:36 AM | Privacy PolicySite Map © 2024 Elevate Software, Inc. All Rights Reserved Questions or comments ? E-mail us at info@elevatesoft.com |