![]() | ![]() Products ![]() ![]() ![]() ![]() |
Home » Technical Support » DBISAM Technical Support » Support Forums » DBISAM Enhancement Requests and Suggestions » View Thread |
Messages 1 to 3 of 3 total |
![]() |
Fri, Aug 3 2007 8:07 AM | Permanent Link |
Arnd Baranowski | Tim,
as I am not the only one playing arround with the maximum number of tables per database. What do you think about making it optional and adding a property? Arnd |
Fri, Aug 3 2007 1:25 PM | Permanent Link |
Tim Young [Elevate Software] Elevate Software, Inc. ![]() | Arnd,
<< as I am not the only one playing arround with the maximum number of tables per database. What do you think about making it optional and adding a property? >> I assume that you're talking DBISAM ? The main issue with making it configurable is the fact that multiple settings with multiple applications could really cause problems if not caught. -- Tim Young Elevate Software www.elevatesoft.com |
Fri, Aug 3 2007 3:59 PM | Permanent Link |
Arnd Baranowski | Tim,
> > I assume that you're talking DBISAM ? Yes > The main issue with making it > configurable is the fact that multiple settings with multiple applications > could really cause problems if not caught. > OK, recompiling causes less headakes. Arnd |
This web page was last updated on Wednesday, July 2, 2025 at 06:46 PM | Privacy Policy![]() © 2025 Elevate Software, Inc. All Rights Reserved Questions or comments ? ![]() |