I'm tellin' ya...I saw that other Temp directory in the PROPERTY value
of the Engine Component (and Session) and that Temp directory did not
exist on my computer (see the Temp directory in the error message I
posted), BUT! the code was the same - nothing different there.  It
could have just been a fluke...I have no idea.

I was using the v2.0b8 Trial (non-unicode) when I reported that and my
other stuff, but as of last night...I uninstalled v2.02b8 once again
and downloaded the new v2.02b9 (unicode) version and all is well now.
I can't explain what happened, but maybe Tim can make sense of it.

Which brings me to a bug I think I found (at least on my side - someone
please confirm this!).  I'm thinking it MAY have something to do with
the previous v2.02b8 NON-Unicode Trial version I had installed before,
but in the Engine (or Session) component now - I cannot change the
ConfigPath via the dialog box.  I click on the button, dialog box pops
up...pick another directory...click OK - and the ConfigPath doesn't
change to the directory I picked.

It was strange as well that when I threw the components up initially in
this v2.02b9 - the ConfigPath Property was set to "c:\cdcollector", so
there's obviously some rogue file or registry setting affecting it from
the previous install even after a full uninstall.

I happened on this last night and tried it again this morning with a
clean startup of Delphi 2007...blank form, Engine component, click to
change the ConfigPath - and it still does not change.  Typing in the
path works, though. Exactly same thing happens with the Session
Component.

Cheers,
Fred

--

Roy Lambert wrote:

> Tim
>
>
> > When did you originally download the trial version ? The code most
> > certainly ships with the temporary tables path being set at runtime
> > in the BeforeEngineStart event, and has done so for as long as I
> > can remember.
>
> Way back I remember having similar issues. In my case I recall (with
> my fallible memory) that it was down to the UseLocalConfigSettings
> property being set wrongly.  I done some experimenting and something
> weird can happen. Open a new project drop an engine component on it.
> Alter UseLocalConfigSettings from its default of False to true. Close
> that project (don't bother to save), open a new one, drop an engine
> component on it and look at UseLocalConfigSettings - its TRUE!!!!!
>
> This can, obviously, cause problems.
>
> Roy Lambert

Fred

>I'm tellin' ya...I saw that other Temp directory in the PROPERTY value
>of the Engine Component (and Session) and that Temp directory did not
>exist on my computer (see the Temp directory in the error message I
>posted), BUT! the code was the same - nothing different there. It
>could have just been a fluke...I have no idea.

Those are the ones that Tim has set on his development machine

>Which brings me to a bug I think I found (at least on my side - someone
>please confirm this!). I'm thinking it MAY have something to do with
>the previous v2.02b8 NON-Unicode Trial version I had installed before,
>but in the Engine (or Session) component now - I cannot change the
>ConfigPath via the dialog box. I click on the button, dialog box pops
>up...pick another directory...click OK - and the ConfigPath doesn't
>change to the directory I picked.

It works fine here on the non-unicode version unless the engine / session is active in which case it throws an error telling you it can't change it.

>It was strange as well that when I threw the components up initially in
>this v2.02b9 - the ConfigPath Property was set to "c:\cdcollector", so
>there's obviously some rogue file or registry setting affecting it from
>the previous install even after a full uninstall.

This will also be a value Tim has set in there whilst developing - it doesn't count since its being overridden on execution.

Roy Lambert [Team Elevate]

Roy,

<< Way back I remember having similar issues. In my case I recall (with my
fallible memory) that it was down to the UseLocalConfigSettings property
being set wrongly. I done some experimenting and something weird can happen.
Open a new project drop an engine component on it. Alter
UseLocalConfigSettings from its default of False to true. Close that project
(don't bother to save), open a new one, drop an engine component on it and
look at UseLocalConfigSettings - its TRUE!!!!! >>

Yes, but that shouldn't occur if there is *already* a TEDBEngine component
on the data module, which is the case here.  The properties for it should be
read from the data module .dfm.

--
Tim Young
Elevate Software
www.elevatesoft.com

Fred,

<< I'm tellin' ya...I saw that other Temp directory in the PROPERTY value of
the Engine Component (and Session) and that Temp directory did not exist on
my computer (see the Temp directory in the error message I posted), BUT! the
code was the same - nothing different there.  It could have just been a
fluke...I have no idea. >>

That's normal - it's actually the temporary directory on my machine.  It
doesn't matter because the runtime code sets the temporary tables path when
the application is run.

<< I was using the v2.0b8 Trial (non-unicode) when I reported that and my
other stuff, but as of last night...I uninstalled v2.02b8 once again and
downloaded the new v2.02b9 (unicode) version and all is well now. I can't
explain what happened, but maybe Tim can make sense of it. >>

Hmm, no idea.

<< Which brings me to a bug I think I found (at least on my side - someone
please confirm this!).  I'm thinking it MAY have something to do with the
previous v2.02b8 NON-Unicode Trial version I had installed before, but in
the Engine (or Session) component now - I cannot change the ConfigPath via
the dialog box.  I click on the button, dialog box pops up...pick another
directory...click OK - and the ConfigPath doesn't change to the directory I
picked. >>

And you're not getting an error message ?  Is the TEDBEngine.Active property
set to True ?

<< It was strange as well that when I threw the components up initially in
this v2.02b9 - the ConfigPath Property was set to "c:\cdcollector", so
there's obviously some rogue file or registry setting affecting it from the
previous install even after a full uninstall. >>

The ConfigPath is not read from the registry, or affected in any way by the
installation process.

<< I happened on this last night and tried it again this morning with a
clean startup of Delphi 2007...blank form, Engine component, click to change
the ConfigPath - and it still does not change.  Typing in the path works,
though. Exactly same thing happens with the Session Component. >>

Okay, now I understand what you're saying (typing vs. dialog).  I'll check
this out for D2007 and see what the issue is.

--
Tim Young
Elevate Software
www.elevatesoft.com

TIM - OK, Let me know if you need me to do any other tests.

Cheers,
Fred

--



Tim Young [Elevate Software] wrote:

> Fred,
>
> << I'm tellin' ya...I saw that other Temp directory in the PROPERTY
> value of the Engine Component (and Session) and that Temp directory
> did not exist on my computer (see the Temp directory in the error
> message I posted), BUT! the code was the same - nothing different
> there.  It could have just been a fluke...I have no idea. >>
>
> That's normal - it's actually the temporary directory on my machine.
> It doesn't matter because the runtime code sets the temporary tables
> path when the application is run.
>
> << I was using the v2.0b8 Trial (non-unicode) when I reported that
> and my other stuff, but as of last night...I uninstalled v2.02b8 once
> again and downloaded the new v2.02b9 (unicode) version and all is
> well now. I can't explain what happened, but maybe Tim can make sense
> of it. >>
>
> Hmm, no idea.
>
> << Which brings me to a bug I think I found (at least on my side -
> someone please confirm this!).  I'm thinking it MAY have something to
> do with the previous v2.02b8 NON-Unicode Trial version I had
> installed before, but in the Engine (or Session) component now - I
> cannot change the ConfigPath via the dialog box.  I click on the
> button, dialog box pops up...pick another directory...click OK - and
> the ConfigPath doesn't change to the directory I picked. >>
>
> And you're not getting an error message ?  Is the TEDBEngine.Active
> property set to True ?
>
> << It was strange as well that when I threw the components up
> initially in this v2.02b9 - the ConfigPath Property was set to
> "c:\cdcollector", so there's obviously some rogue file or registry
> setting affecting it from the previous install even after a full
> uninstall. >>
>
> The ConfigPath is not read from the registry, or affected in any way
> by the installation process.
>
> << I happened on this last night and tried it again this morning with
> a clean startup of Delphi 2007...blank form, Engine component, click
> to change the ConfigPath - and it still does not change.  Typing in
> the path works, though. Exactly same thing happens with the Session
> Component. >>
>
> Okay, now I understand what you're saying (typing vs. dialog).  I'll
> check this out for D2007 and see what the issue is.

Tim

><< Way back I remember having similar issues. In my case I recall (with my
>fallible memory) that it was down to the UseLocalConfigSettings property
>being set wrongly. I done some experimenting and something weird can happen.
>Open a new project drop an engine component on it. Alter
>UseLocalConfigSettings from its default of False to true. Close that project
>(don't bother to save), open a new one, drop an engine component on it and
>look at UseLocalConfigSettings - its TRUE!!!!! >>
>
>Yes, but that shouldn't occur if there is *already* a TEDBEngine component
>on the data module, which is the case here. The properties for it should be
>read from the data module .dfm.

Didn't try, have now and you wont like the answer! However, it shouldn't do it regardless. There should be no difference in the properties of a component dropped on a form from a clean start of the IDE and after doing things in it.

D2006 - my test

Open IDE, start new project drop engine on form alter UseLocalConfigSettings to True, close project without saving. Open CDCollector (do you really own those albums?) open datamodule - UseLocalConfigSettings is TRUE!. Close IDE open IDE open CDCollector open datamodule UseLocalConfigSettings is FALSE.

Roy Lambert

TIM - one other thing not related to this issue:

Is there any particular reason why the ANSI (non-Unicode) examples are
also included in the UNICODE downloads?  Both ANSI and UNICODE examples
for "cdcollector" and "demos" are inside the "examples" folder.

If no particular reason, then can I make a suggest to only include the
UNICODE examples only (in the UNICODE download only) as I could see
other folks (esp new EDB users) accidentally opening the wrong (ANSI)
folder and vice-versa with the ANSI downloads.

I would also suggest splitting up the Admin Tools as well.  When
clicking on EDB Manager...I've already accidentally clicked on the ANSI
version when I have the UNICODE version of the components installed.

I'm sure this probably means more work on your side to compile the
stuff, but I just wanted to throw that out there as a small suggestion
to help eliminate human error if indeed there's no particular reason
why both types of examples are installed in each ANSI and UNICODE
downloads.

Cheers!
Fred

--



Fred H. wrote:

> TIM - OK, Let me know if you need me to do any other tests.
>
> Cheers,
> Fred

Roy,

<< Didn't try, have now and you wont like the answer! However, it shouldn't
do it regardless. There should be no difference in the properties of a
component dropped on a form from a clean start of the IDE and after doing
things in it.

D2006 - my test

Open IDE, start new project drop engine on form alter
UseLocalConfigSettings to True, close project without saving. Open
CDCollector (do you really own those albums?) open datamodule -
UseLocalConfigSettings is TRUE!. Close IDE open IDE open CDCollector open
datamodule UseLocalConfigSettings is FALSE. >>

I'll check this out and let you know what I find.

--
Tim Young
Elevate Software
www.elevatesoft.com

Fred,

<< Is there any particular reason why the ANSI (non-Unicode) examples are
also included in the UNICODE downloads?  Both ANSI and UNICODE examples for
"cdcollector" and "demos" are inside the "examples" folder. >>

It's just the way the build system works - the examples are built per
ElevateDB product, not per target compiler.

<< If no particular reason, then can I make a suggest to only include the
UNICODE examples only (in the UNICODE download only) as I could see other
folks (esp new EDB users) accidentally opening the wrong (ANSI) folder and
vice-versa with the ANSI downloads. >>

I'll see what I can do.

--
Tim Young
Elevate Software
www.elevatesoft.com

Roy...just to let you know that as of Friday, I'm a bonifide member of
the ElevateDB club.  unfortunately you'll be seeing my ugly face
more often....when I'm not in hibernation, which lucky you...is most of
the time. LOL

Anyway...thanks again for all your help...I need to get started
converted all my DBISAM apps now and I'm sure I'll be back with more
questions.

TIM - keep up the excellent work and look forward to you making
ElevateDB great with alot of features!  Being Embarcadero is a DB
company in itself...lots of companies/folks tend to forget the "little
man" like myself that need a straight-forward, relatively
easy-to-understand (and to be able to connect easily) database that is
also easy to deploy...for simple and bigger apps.

All the best,
Fred

--



Roy Lambert wrote:

> Fred
>
>
> It sounds that like myself you really hammer some of the ease of use
> functionality that was built into DBISAM.
>
> The "problem" with ElevateDB is that its an implementation of
> SQL:2003 or as I once posted "big box". If you're used to DBISAM its
> going to take a lot of getting your head round. Once you do you'll
> find it has a lot more features and in some areas is a lot faster.
> You'll also find you have less hair than when you started
>
> > 1) I really use the RENAME and COPY table (and column) function in
> > DBISAM, but how to do this in EDBv2?
>
> You can't. Tim has promised these, they're in the roadmap, but there
> are definite problems. Things that ElevateDB has that DBISAM doesn't
> are referential integrity, triggers, views and stored procedures. SO
> in DBISAM a table was pretty much stand alone in database terms,
> anything you did to it it was your responsibility to sort out your
> programs to match it. With ElevateDB a table or a column could be
> referenced all over the place so altering it can have major
> consequences and its now Tim's (ie ElevateDB's) responsibility to
> sort it out.
>
> The only thing you can do is drop the appropriate object (table or
> column) having first altered all the RI, triggers etc, create a new
> one and then recreate the RI etc if wanted.
>
> > In the EDB Manager...ALTER (table) does not allow to change the
> > name of a table, nor is there any function to copy/rename a table
> > either! This is really a deal killer for me and I'm very surprised
> > such functions haven't made it in v2 at least. This is the main
> > reason why I did not evaluate v1 any further. Same thing with
> > changing column names in a table - can't do it!
>
> See above
>
> > 2) I've looked everywhere in the help files and forum, but I cannot
> > for the life of me find out a plain jane way to deploy a local
> > application for ElevateDB to other users.
>
> Not difficult - I assume you're talking fileserver in which case the
> CD Collector example is good.
>
> > Here's my situation - I've got 1 database structure, but multiple
> > databases that need to be opened on the client side (one at a
> > time). So using DBISAM, I compile the application and there's a SQL
> > routine to create a new database and also to open an existing
> > database.  To open another database....just click Open, point to
> > another database folder...it then closes the open database and
> > opens that new one.
> >
> > How is this actually accomplished using ElevateDB with Session,
> > Config file, Catalogs...and apparently a "server" executable file?
>
> ElevateDB uses databases - stand alone tables are a thing of the past
> (or a thing of DBISAM - every table is now a part of a database.
>
> What you have in ElevateDB is configuration files holding the high
> level details (databases, users etc) associated with one or more
> catalogs which hold the table metadata etc.
>
> In terms of components think of the following
>
> TEDBEngine
> All I do with this is set the UseLocalConfigSettings to True so that
> the settings I define in the session component are used.
>
> TEDBSession
> Set the LocalConfigPath, user name and password (see below) and
> session name
>
> TEDBDatabase
> This is where the real work starts set the session name, databasename
> and database The database must have been created prior to this using
> CREATE DATABASE name PATH path (you can alter the database path using
> ALTER DATABASE but not if its being used)
>
> TEDBTable
> Set the sessionname, databasename, tablename and table
>
> Its a "bit" more involved than in DBISAM but still manageable (I just
> scream quietly every time I just want to check something out and I
> need to hook up a table to try something)
>
> If the necessary databases with the paths are created in the config
> then when you have things set up properly on a form it will simply be
> a matter of close TEDBDatabase, set TEDBDatabase to a new database
> and open.
>
> > 3) I don't get the Login bit when creating (or editing) a new
> > Session in EDB Manager.  There's a Login page/tab to enter a
> > username and password, but I can't find the explanation what that
> > is actually for as the only way to open the Session was to use the
> > default "Administrator" and "EDBDefault" password...despite
> > whatever I put on the Login page/tab.
>
> Administrator is built in (as is System), if you want to use
> something of your own you need to create a user in the session. In
> EDBManager go to the session and you should see a list underneath it
> which will include Users, click on that and to the right you will see
> the prompt Create new user. Click on that and you can create a user.
> Depending what you want to do you may have to create and allocate a
> Role as well. New users are granted the Public role.
>
> Finally you can define which users / roles can do what to the
> database. Its very confusing to someone who hasn't operated a similar
> system before. My advice would be either stick to the Administration
> user or add any you create to the administrator's role so they get
> full access to the database. You can alter this later on as you get
> more familiar and if you need it.
>
> > Also...when closing it and re-opening it...I have to type all that
> > over again which is a bit cumbersome, so is there a way to save
> > that without having to re-enter it everytime?
>
> Yeah - put it into the TEDBSession and save it with the app. Its a
> departure from my usage of DBISAM but anything I do now I drop an
> engine, session, at least one database and table component onto a
> datamodule and set them up in the IDE. Alternatively you can set in
> code.
>
> > I apologize for my stupidity, but having used DBISAM for so long
> > now....I'm really having trouble wrapping my head around ElevateDB
> > and I'm finding the little things I loved in DBISAM are missing in
> > ElevateDB.
>
> Two years or so downstream I'm getting my head round it but DBISAM
> had matured with a lot of ease of use features. I know some (eg IF
> EXISTS) will not emerge in ElevateDB but I'm hoping others will, and
> I know some are on the roadmap.
>
> Overall the transition was non-trivial but worth it.
>
> Roy Lambert [Team Elevate]