Aaron,

<< I don't think it needs repeating, it's bleedingly obvious, Tim >>

Yeah, that was more for everyone else reading.

--
Tim Young
Elevate Software
www.elevatesoft.com

Aaron,

<< If you have a config file already created, filled with users and roles
and all that good stuff, what's the difference between having to set the
path of the ElevateDB config file vs having to set the path of the DBISAM
database? >>

The configuration file is the "system" or "master" database for the entire
application.  Think of it as being the same as where you would put the
system settings for databases, etc. in DBISAM.  In fact, at some point I'll
most likely expand the config file usage so that it allows you to store your
own system-wide data in it.

<< It's kinda rhetorical - it's clear you have no interest in making the 2
databases work the same way. I forgot for a second the path to the config
file, as you requested. But my version control workflow, of copying an
entire application directory and renaming it to Version n+1 requires me to

* change the config file location in EDB manager
* change the config file location in EDBEngine

each time I version the app, and I need code in the start up of the
application that checks current db path, comparing it to current application
path, and updating as required.

In DBISAM, well, I would just always set the path to {app}\data. >>

Yes, in that case you will need to modify the configuration file path
constantly.  However, you do have to realize that this type of constant
modification to the core application directory is somewhat unusual and most
people keep the same directory structure, once-established.

<< This is not a rant now, but a bit more background on where I am coming
from. I just migrated to D2010 from D7, and none of the 3rd party controls I
had been using worked, so my rant above is the culmination of a week of
pulling my hair out, no offense intended. >>

Yeah, that seems to be the case with most customers, to which I say "I feel
your pain".   I'm just now settling down from simply switching my
development machine from XP to 64-bit Windows 7, and it has tried my
patience at times.

--
Tim Young
Elevate Software
www.elevatesoft.com

Tim,

> The configuration file is the "system" or "master" database for the entire
> application.  Think of it as being the same as where you would put the
> system settings for databases, etc. in DBISAM.

> In fact, at some point I'll most likely expand the config file usage so
> that it allows you to store your own system-wide data in it.

Yes please.  At least a CLOB field where we can store information about a
database at the database object level would be very appreciated.   

--

---------------------------------------
 Terry Swiers
 Millennium Software, Inc.
 http://www.1000years.com
 http://www.atrex.com

 The Atrex 13 beta is now available.
 Visit http://v13beta.atrex.com for more information.

Atrex Electronic Support Options:
 Atrex Knowledgebase: http://www.atrex.com/atrexkb.asp
 Email: mailto:support@atrex.com
 Newsgroup: news://news.1000years.com/millennium.atrex
 Fax: 1-925-829-1851
 Phone: 1-925-828-5892 (M-F, 9a-5p Pacific)
 ---------------------------------------

Lance

>While I have TMS as well, It's always been hit and miss for stability. And miss for documentation. I've really liked the work done by DevExpress and their stuff works nicely with ElevateDB.

DevEx is way to expensive for a mere hobbyist. I bought TMS 1) because they had the planner and 2) to get a complete suite with the same nice modern look and feel that users could customise. Most of its fine, even though I'll never use all the facilities, but the DBAdvGrid is driving me mad. My current plan is to use Mike Skolnik's freeware grid and build in the prettyness and desired features it lacks myself.

Roy Lambert