Login ProductsSalesSupportDownloadsAbout |
Home » Technical Support » DBISAM Technical Support » Support Forums » DBISAM Enhancement Requests and Suggestions » View Thread |
Messages 1 to 4 of 4 total |
Essentials component |
Sat, Feb 2 2008 10:13 AM | Permanent Link |
Roy Lambert NLH Associates Team Elevate | Tim
I just wanted to test something out and I've ended up analysing my reluctance to do a quick "check it out" with ElevateDB. What I wanted to do was a test with the TDBAdvStringGrid to see if in some areas I could get away from memory tables and just use queries. With DBISAM (sorry) I would have dropped a grid and a TDBISAMQuery on the form, set the directory, banged in some sql and away we go. With ElevateDB I drop a TEDBEngine, a TEDBSession, a TEDBDatabase and a TEDBQuery on the form. Set the engines ConfigPath to the directory, set the sessions LoginUser, LoginPassword and SessionName. Set the databases SessionName, DatabaseName and Database. Finally set the query's SessionName and DatabaseName. Then bang in some sql and off we go. No problems with doing this for a real app but its an annoyance for a quick and dirty test. I don't know if this would even be possible but I was thinking a component that held the bits that are needed, possibly stored them somewhere (I hate to suggest the registry but I will) so that you dropped the other components on then this one and it went and filled in the necessary bits. If it couldn't store them at least it would be only one place to enter the bumph. I know that on some occasions you might need multiple databases or sessions but I do a lot of "let me just see if that works" type of stuff and it would be really really handy. Roy Lambert |
Sat, Feb 2 2008 10:28 AM | Permanent Link |
"Fons Neelen" | Hi Roy,
> With ElevateDB I drop a TEDBEngine, a TEDBSession, a TEDBDatabase and a > TEDBQuery on the form. Set the engines ConfigPath to the directory, set > the sessions LoginUser, LoginPassword and SessionName. Set the databases > SessionName, DatabaseName and Database. Finally set the query's > SessionName and DatabaseName. Then bang in some sql and off we go. Why not build a small app with the basic stuff you mentionned above, save it, and use it as a "template" app from that point on. Thus, anytime you want to test something you alwas have the basic skeleton ready. Just a suggestion. Fons |
Sat, Feb 2 2008 11:08 AM | Permanent Link |
Roy Lambert NLH Associates Team Elevate | Fons
I have about 5 of those already Roy Lambert |
Mon, Feb 4 2008 3:45 PM | Permanent Link |
Tim Young [Elevate Software] Elevate Software, Inc. timyoung@elevatesoft.com | Roy,
<< I don't know if this would even be possible but I was thinking a component that held the bits that are needed, possibly stored them somewhere (I hate to suggest the registry but I will) so that you dropped the other components on then this one and it went and filled in the necessary bits. >> I'll see if I can add a template for a basic ElevateDB application. That way it would get added to the repository during installation. -- Tim Young Elevate Software www.elevatesoft.com |
This web page was last updated on Friday, April 19, 2024 at 07:09 AM | Privacy PolicySite Map © 2024 Elevate Software, Inc. All Rights Reserved Questions or comments ? E-mail us at info@elevatesoft.com |