Fred,

<< 1) I really use the RENAME and COPY table (and column) function in
DBISAM, but how to do this in EDBv2? >>

You can copy the structure of tables (for the most part - indexes and
triggers not included) using the CREATE TABLE LIKE extensions, and then use
an INSERT INTO..SELECT statement to populate them.

As for renaming - you can't yet.  2.03 will have this functionality (please
don't ask for an ETA).

<< 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! >>

Neither of these things are in the SQL-2003 standard, which is what EDB was
designed for.  The idea was to get the base product in place according to
the standard and then proceed from there.  Unfortunately, some things like
the renaming have taken a bit longer than planned to get implemented.

<< 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. >>

It's deployed in the same fashion as a DBISAM application.  The only
difference is the inclusion of an addition file (the database catalog) for
each database.  For an example of how to create databases on the fly, see
the CDCollector example application that comes with ElevateDB.

<< 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. >>

This also works in the exact same way as a DBISAM application, except for
one difference - you have to create the database in the configuration using
the CREATE DATABASE statement first.  That statement tells ElevateDB where
the database is on disk.

<< 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. >>

That is the default user and password, so of course it is the only option to
start with when you're dealing with a new configuration:

http://www.elevatesoft.com/manual?action=mantopic&id=edb2sql&category=0&topic=8

<< 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? >>

Edit Session/Login.

--
Tim Young
Elevate Software
www.elevatesoft.com

My reply last night was just before I went to bed. In re-reading it I
realized I might have been a little ambiguous.
I should have included a little bit of additional information.

The network configuration utility is rarely used by an end-user as my
installation program takes the variable of where the EDB configuration
files are installed by the end-user and completes the INI file
appropriately. In the case of those who might want to install my
application as a local application on a jump drive or portable hard
drive, they would have the need to alter the INI file to point
correctly to the EDB configuration files.

Fred, I too had a bit of difficulty in getting my head around ElevateDB
(I have been "playing" with it since it first came out) after writing
everything in the past in DBISAM (since v3.x). Then finally after
reading, printing out and re-reading all the helpful posts from Roy and
Tim in this forum, the light bulb over my head finally began to flicker.

I completed my first ElevateDB application which I just distributed. My
installation program allows the options for the end-user to install as
a client/server or local database, and places all the files,
distributables, etc. in the correct locations and completes the
appropriate property configuration settings. To my utter amazement, all
works.

Tim, that's GREAT news about the renaming capabilitites set for v2.03.
Keep up the great work. I'm finally starting to see capabilities in EDB
far beyond what DBISAM had to offer.

--
Regards,
Jan Ferguson [Team Elevate]

Slowly getting there, Roy.  I moved and renamed the "data" directory to c:\cdcollector -
builds OK, but when trying to run it within D2007...I get the following error now:

"ElevateDB Error #600 File manager error (Cannot create file
C:\DOCUME~1\TIMELE~1.000\LOCALS~1\Temp\ME28561392CDCollector4.EDBTbl (OS Error: The system
cannot find the path specified."

I changed the Temp directory in the Engine Component to somewhere under My Documents -
rebuild...still the same problem.  I cannot find anywhere else in the components where
it asks for a Temp directory either, but even after changing the Engine Temp
directory....I still get that error with that previous Temp Directory.

I'm going to uninstall and reinstall the trial version as I'm afraid I may have already
screwed up the project trying to change things here and there to get it to work.

It's not very clear, but exactly what are we supposed to do to get this "cdcollector" app
working in its default location (examples folder) as obviously the Temp Directory that is
in the Engine Component...does not exist on my computer.

I'm trying here, Roy...I really want to get this thing working!!  As far as the code is
concerned...I haven't touched it - it's whatever came with the trial version
(non-unicode).  Just opened it up in Delphi 2007, compiled it and started getting those
errors.

Thanks,
Fred


>OK Roy....tried out the CD Collector app...but I can't get the dang the working. <sigh>
>
>I can build the app (non unicode version) with no problems (using D2007 here), but when I
>tried to run it - I get this error:
>
>"ElevateDB Error #600 File manager error (Cannot create file
>c:\cdcollector\EDBConfig.EDBCfg (OS Error: The system cannot find the path specified."

That error looks clear enough so I apologise for asking the obvious questions

1. Do you have a path c:\cdcollector\
2. Do you have the necessary rights to it?

I've just built and run it from its install directory ( in my case
C:\3rdParty\ElevateDB\examples\cdcollector) and there's no trouble. Moved it
to c:\cdcollector and still no trouble.

>I've done a complete search in the "ElevateDB VCL Trial" directory and the only
>"EDBConfig" file I found was this one: edbconfig.dcu

I don't know where that one is from but when CDCollector starts it should create
EDBConfig.EDBCfg  .EDBLog  .EDBLck but as your error states it can't create them.

>I did manage to convert one of my DBISAM v4 databases, but replacing and changing over the
>DBISAM components to ElevateDB proved to be not very friendly (got stuck in Form text mode
>with an error). Anyway....got things up and running with new components all hooked up
>(simple app)....threw everything over to my 2nd laptop....no go - crashes, won't even
>open. I left the app in the original directory and data directory under it....Config file
>directory on top of the app directory.....so same structure, different computer = no go.

If you want to email me your source for this app I'll have a look at it, see if I can sort
it out and send it back to you working.

Roy Lambert [Team Elevate]

Fred

>Slowly getting there, Roy. I moved and renamed the "data" directory to c:\cdcollector -
>builds OK, but when trying to run it within D2007...I get the following error now:
>
>"ElevateDB Error #600 File manager error (Cannot create file
>C:\DOCUME~1\TIMELE~1.000\LOCALS~1\Temp\ME28561392CDCollector4.EDBTbl (OS Error: The system
>cannot find the path specified."

Is this -  C:\DOCUME~1\TIMELE~1.000\LOCALS~1\ - your temp directory?

>I changed the Temp directory in the Engine Component to somewhere under My Documents -
>rebuild...still the same problem. I cannot find anywhere else in the components where
>it asks for a Temp directory either, but even after changing the Engine Temp
>directory....I still get that error with that previous Temp Directory.

Look in the data DataModule procedure CDCollectorEngineBeforeStart - this is where Tim is setting directories. If you set them on the engine component in the IDE they will be overridden by this when the app starts. The one below it DataModuleCreate is where Tim sets the directory for the data and it should just hang off the application directory as \data.

>It's not very clear, but exactly what are we supposed to do to get this "cdcollector" app
>working in its default location (examples folder) as obviously the Temp Directory that is
>in the Engine Component...does not exist on my computer.

As I said above the temp directory is set at run time and unless Tim was smoking something interesting at the time I'd guess his code simply asks the OS for the temp dir.

To make it work from its install folder - Load - compile - run. At least that's all I'm doing here.

Have you altered UseLocalSessionEngineSessions from False in the engine either in the IDE or anywhere in your code? I know I said I do in my apps but Tim hasn't in this one and the session temp folder looks just like the one you're being told about (so does the one in the engine but that is GUARANTEED to be changed). I seem to recall this happening to me once.

More questions (wether they'll help or not I don't know)

1. what OS
2. are you running a VM
3. you downloaded and installed the non-unicode trial - you are using the non-unicode demo
4. 32bit or 64bit OS

>I'm trying here, Roy...I really want to get this thing working!! As far as the code is
>concerned...I haven't touched it - it's whatever came with the trial version
>(non-unicode). Just opened it up in Delphi 2007, compiled it and started getting those
>errors.

I remember I had some fun when I started. If Tim had lived round the corner rather than in another country he would have written no more code!

Roy Lambert [Team Elevate]

JAN - thanks alot for your input and yep...I feel like an idiot and Tim has coded the
whole thing and I'm just having a hard time understanding it!  I'm persistent though and
while I may not sleep well at night dreaming of how all this works....the nut will
(hopefully) hit my head this week and I can sleep better. LOL

ROY - I finally got the "cdcollector" demo working after uninstalling it and reinstalling
the demo....so all that worked like it's supposed to have...I have no idea why it wouldn't
work the first time I installed it (I never changed anything).  Now it's time to
deconstruct it and my first step is figuring out this whole Config file way of doing
things and taking that app and making it work on another computer.  From there....I'll
then wrap my head around opening a different database with the same/different data in it,
but in a different location....which I gather I need to use the ALTER DATABASE statement.

I really just don't have the time to learn something completely new (or dread the day I
need to convert everything over!).  It was painful enough to go from v3 to v4 in
FastReports, so I just HOPE if I decide to pay for ElevateDB and upgrade all the DBISAM
apps I have....that it won't be as painful.  

But to answer your reply, Roy - YES, confirmed that the Temp Directory mentioned is
indeed, by default, in the Temp property in the Engine Component (not my Temp directory),
but looking at the code - in the BeforeEngineStart routine - "GetTempPath" must override
that property as it "gets/uses" the default temporary directory for the OS (according to
the manual), so I guess it doesn't matter what's in there and the code overrides it.

FYI - I'm using WinXP 32bit on that laptop in which I'm testing ElevateDB out; I've got
another lappy with Vista Business 32bit on it, so....now I will try to take that compiled
"cdcollector" app with the database and move it to this laptop and see if I can get it
running.  Basically to simulate my other apps that I distribute to our guys overseas.

TIM  - For my own good measure and curiosity, though, I am checking out NexusDB (Embedded
free) as well right now to get a feel of what it's all about.  I understand it's SQL 2003
compliant as well and when trying out their "Enterprise Manager"...I was able to rename
and copy a basic table with no constraints like in DBISAM and pretty much got a DBISAM app
up and running (using their conversion tool), so does that mean either of you have
different interpretations of SQL 2003?  Either way....that's great news you're working on
getting the RENAME/COPY function in there.

I have no idea the advantages or disadvantages btw ElevateDB and NexusDB, so I would
really like to hear your plug on that.  I don't want to change from you guys at all as I
really need RI support now + the fact that ElevateDB is obviously where you are devoting
your future to so I feel the need to upgrade or change now to have something current and
keep up.  In the end, I just need/want something fairly simple and not be too over my head
that I have to re-learn a whole new system with the ability to have a couple/few people
access a database at the same time.  I really feel like an idiot right now and I only wish
this stuff came to me naturally like it does for you guys.

Many Thanks,
Fred

Fred,

<< ROY - I finally got the "cdcollector" demo working after uninstalling it
and reinstalling the demo....so all that worked like it's supposed to
have...I have no idea why it wouldn't work the first time I installed it (I
never changed anything). >>

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.

<< Now it's time to deconstruct it and my first step is figuring out this
whole Config file way of doing things and taking that app and making it work
on another computer.  From there....I'll then wrap my head around opening a
different database with the same/different data in it, but in a different
location....which I gather I need to use the ALTER DATABASE statement. >>

No, you don't need to use ALTER DATABASE when just switching to a different
database.  You do so just like with DBISAM - close the old database and open
the new one.   You only use CREATE DATABASE when first creating the
database.   Just remember that you use CREATE DATABASE whenever you create
the database directory in which the database will reside.  You could even
just name the databases with the same name as the database directories.

<< But to answer your reply, Roy - YES, confirmed that the Temp Directory
mentioned is indeed, by default, in the Temp property in the Engine
Component (not my Temp directory), but looking at the code - in the
BeforeEngineStart routine - "GetTempPath" must override that property as it
"gets/uses" the default temporary directory for the OS (according to the
manual), so I guess it doesn't matter what's in there and the code overrides
it. >>

Yes, that is how it works.

<< TIM  - For my own good measure and curiosity, though, I am checking out
NexusDB (Embedded free) as well right now to get a feel of what it's all
about.  I understand it's SQL 2003 compliant as well and when trying out
their "Enterprise Manager"...I was able to rename and copy a basic table
with no constraints like in DBISAM and pretty much got a DBISAM app up and
running (using their conversion tool), so does that mean either of you have
different interpretations of SQL 2003?  Either way....that's great news
you're working on getting the RENAME/COPY function in there. >>

No, it means that they have extended the SQL standard, just like we have in
various ways.

<< I have no idea the advantages or disadvantages btw ElevateDB and NexusDB,
so I would really like to hear your plug on that.  >>

I'm sorry, but we don't comment on competitor's products.  We let the
products and support/service stand on their own merits.

--
Tim Young
Elevate Software
www.elevatesoft.com

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. >>

I had downloaded it a couple of days ago and reinstalled the same version, so no idea what
happened, the main thing is I got it working now.

<< No, you don't need to use ALTER DATABASE when just switching to a different
database.  You do so just like with DBISAM - close the old database and open
the new one.   You only use CREATE DATABASE when first creating the
database.   Just remember that you use CREATE DATABASE whenever you create
the database directory in which the database will reside.  You could even
just name the databases with the same name as the database directories. >>

OK cool....will play around with all that and any questions, will post in a new thread
(this one's starting to get a bit long in the tooth!)

<< Yes, that is how it works. >>

great...at least I now know that it works like that.

<< No, it means that they have extended the SQL standard, just like we have in
various ways. >>

OK I see.

<< I'm sorry, but we don't comment on competitor's products.  We let the
products and support/service stand on their own merits. >>

Fair enough...no problem.

One final clarification, Tim - there's no option in my Customer Area to go straight to
EDBv2 C/S (without source).  According to your Promo email....it's the same price for Std
source or no source and the same price for C/S source or no source.

Below are the only EDB upgrade options I see in my account, but nothing for upgrading to
Client/Server (I MAY jump straight up to C/S no source).

UPG1TO2 - To EDB-VCL-STD
UPG2STD - To EDB-VCL-STD-SRC

Thanks!
Fred

Fred,

<< One final clarification, Tim - there's no option in my Customer Area to
go straight to EDBv2 C/S (without source).  According to your Promo
email....it's the same price for Std source or no source and the same price
for C/S source or no source. >>

Contact Sam in sales (sales@elevatesoft.com) and she'll help you with the
pricing.  I don't want to quote you a price because I normally screw it up.


--
Tim Young
Elevate Software
www.elevatesoft.com

<< Contact Sam in sales (sales@elevatesoft.com) and she'll help you with the
pricing.  I don't want to quote you a price because I normally screw it up.
>>

LOL...OK will do!

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