I installed the trial for EDB and most (but not all) of the demos throw the
same exception "Project xxx.exe raised exception class EEDBException with
message 'ElevateDB Error #406 Invalid temporary table identifier' when I try
to run them.

the following demos work:

- GUID
- jpegBlob
- masterdetail
- simpletable
- triggers

all other demos throw the same exception #406 (including the CD collector
demo)

I did not test the simplequery demo

running D7.1 under XP SP2

- Stephane

I am having a very similar experience. I'm running D7 on XP home.

Hi Guys,

I wrote all the sample applications (except for CD collector), and tested
them extensively before handing over to Tim, but you've obviously stumbled
on something that slipped by First of all, you don't mention it, but
have you run the CreateDBDDL sample? I assume you have. This creates the
datafolder and DB. If you haven't, this could be the cause of your problem.
The demos you mention are table based and therefore would not cause any
temporary tables to be created. When each of the applications start, the
temporary folder is set to the data location (coz I know this should exists,
and it makes the apps generic) I am guessing that there might be a rights
issue for that folder, or the folder does not yet exist.

--
Best regards

Steve

"Stephane Perron" <misterz at videotron dott ca> wrote in message
news:D02DCFE5-B1B6-482E-9048-B0DF4FCB5C05@news.elevatesoft.com...
>I installed the trial for EDB and most (but not all) of the demos throw the
>same exception "Project xxx.exe raised exception class EEDBException with
>message 'ElevateDB Error #406 Invalid temporary table identifier' when I
>try to run them.
>
> the following demos work:
>
> - GUID
> - jpegBlob
> - masterdetail
> - simpletable
> - triggers
>
> all other demos throw the same exception #406 (including the CD collector
> demo)
>
> I did not test the simplequery demo
>
> running D7.1 under XP SP2
>
> - Stephane
>
>
>
>
>

Hi,

So you are THE Steve Forbes.

I've noticed that some of the demos have the ConfigPath property of their
TEDBEngine component pointing to "C:\Documents and Settings\steveforbes"
and the TempTablesPath property of the same component pointing to
"C:\DOCUME~1\STEVEF~2\LOCALS~1\Temp\". Obviously, these paths don't exist on
my machine. I've tried to change them to a valid one (so I think) but it
didn't help.

All the demos with that ConfigPath value throw the exception. It might be
linked to the problem.

I didn't have time (yet) to look at the code and check if those properties
are changed when the program runs.

The working demos have the ConfigPath property pointing to c:\demos\data,
which is also invalid on my machine. The TempTablesPath also points to
"C:\DOCUME~1\STEVEF~2\LOCALS~1\Temp\". Still, those demos work fine.

BTW, the CreateDBDDL sample also throws the exception so I cannot run it.

I'm still working on the problem. I will look at the code itself. It's a
good way to learn more about EDB...   

Regards,

Stephane


"Steve Forbes" <ozmosys@spamfreeoptusnet.com.au> wrote in message
news:76DC32D1-6AD6-42B2-A5F6-A87C1BAD6A78@news.elevatesoft.com...
> Hi Guys,
>
> I wrote all the sample applications (except for CD collector), and tested
> them extensively before handing over to Tim, but you've obviously stumbled
> on something that slipped by First of all, you don't mention it, but
> have you run the CreateDBDDL sample? I assume you have. This creates the
> datafolder and DB. If you haven't, this could be the cause of your
> problem. The demos you mention are table based and therefore would not
> cause any temporary tables to be created. When each of the applications
> start, the temporary folder is set to the data location (coz I know this
> should exists, and it makes the apps generic) I am guessing that there
> might be a rights issue for that folder, or the folder does not yet exist.
>
> --
> Best regards
>
> Steve
>
> "Stephane Perron" <misterz at videotron dott ca> wrote in message
> news:D02DCFE5-B1B6-482E-9048-B0DF4FCB5C05@news.elevatesoft.com...
>>I installed the trial for EDB and most (but not all) of the demos throw
>>the same exception "Project xxx.exe raised exception class EEDBException
>>with message 'ElevateDB Error #406 Invalid temporary table identifier'
>>when I try to run them.
>>
>> the following demos work:
>>
>> - GUID
>> - jpegBlob
>> - masterdetail
>> - simpletable
>> - triggers
>>
>> all other demos throw the same exception #406 (including the CD collector
>> demo)
>>
>> I did not test the simplequery demo
>>
>> running D7.1 under XP SP2
>>
>> - Stephane
>>
>>
>>
>>
>>
>
>

One slight correction :

I just uninstalled/reinstalled EDB and tried the CreateDBDDL sample again..

The Createdbddl sample will create a batch of files in the data folder then
will throw the #406 exception. It also throws the exception if I click the
Delete Tables button after running the demo again.

No changes for working/non working demos after reinstalling EDB.

Stéphane

"Stephane Perron" <misterz at videotron dott ca> wrote in message
news:B065397A-0AD9-44F7-ACAF-17B59175DAE4@news.elevatesoft.com...
> Hi,
>
> So you are THE Steve Forbes.
>
> I've noticed that some of the demos have the ConfigPath property of their
> TEDBEngine component pointing to "C:\Documents and Settings\steveforbes"
> and the TempTablesPath property of the same component pointing to
> "C:\DOCUME~1\STEVEF~2\LOCALS~1\Temp\". Obviously, these paths don't exist
> on my machine. I've tried to change them to a valid one (so I think) but
> it didn't help.
>
> All the demos with that ConfigPath value throw the exception. It might be
> linked to the problem.
>
> I didn't have time (yet) to look at the code and check if those properties
> are changed when the program runs.
>
> The working demos have the ConfigPath property pointing to c:\demos\data,
> which is also invalid on my machine. The TempTablesPath also points to
> "C:\DOCUME~1\STEVEF~2\LOCALS~1\Temp\". Still, those demos work fine.
>
> BTW, the CreateDBDDL sample also throws the exception so I cannot run it.
>
> I'm still working on the problem. I will look at the code itself. It's a
> good way to learn more about EDB...   
>
> Regards,
>
> Stephane
>
>
> "Steve Forbes" <ozmosys@spamfreeoptusnet.com.au> wrote in message
> news:76DC32D1-6AD6-42B2-A5F6-A87C1BAD6A78@news.elevatesoft.com...
>> Hi Guys,
>>
>> I wrote all the sample applications (except for CD collector), and tested
>> them extensively before handing over to Tim, but you've obviously
>> stumbled on something that slipped by First of all, you don't
>> mention it, but have you run the CreateDBDDL sample? I assume you have.
>> This creates the datafolder and DB. If you haven't, this could be the
>> cause of your problem. The demos you mention are table based and
>> therefore would not cause any temporary tables to be created. When each
>> of the applications start, the temporary folder is set to the data
>> location (coz I know this should exists, and it makes the apps generic) I
>> am guessing that there might be a rights issue for that folder, or the
>> folder does not yet exist.
>>
>> --
>> Best regards
>>
>> Steve
>>
>> "Stephane Perron" <misterz at videotron dott ca> wrote in message
>> news:D02DCFE5-B1B6-482E-9048-B0DF4FCB5C05@news.elevatesoft.com...
>>>I installed the trial for EDB and most (but not all) of the demos throw
>>>the same exception "Project xxx.exe raised exception class EEDBException
>>>with message 'ElevateDB Error #406 Invalid temporary table identifier'
>>>when I try to run them.
>>>
>>> the following demos work:
>>>
>>> - GUID
>>> - jpegBlob
>>> - masterdetail
>>> - simpletable
>>> - triggers
>>>
>>> all other demos throw the same exception #406 (including the CD
>>> collector demo)
>>>
>>> I did not test the simplequery demo
>>>
>>> running D7.1 under XP SP2
>>>
>>> - Stephane
>>>
>>>
>>>
>>>
>>>
>>
>>
>
>

Hi Stephane,

> So you are THE Steve Forbes.

Yep, that's me .. I'm a virus distibuted with the ElevateDB product <bg>

The problem with the ConfigPath value is related to the Delphi problem of
not being able to stream blank string property values. I tried to empty the
ConfigPath and TempTablesPath for all samples, but the "personalised"
setting automagically reappeared. Incidentally, Tim said he is going to
rewrite the component streaming for these two properties so they behave as
expected. I am sure you will agree, the current situation looks messy.

Both ConfigPath and TempTablesPath are assigned at runtime in the base
form's FormCreate (see DemoFormBase.pas in the Common folder) to get around
the problem.

I would suggest first checking to see if there is a Data folder under the
demos folder coz this is where the data, and the temporary files will be
located. If there is, I would then check that nothing is blocking the
creation of files in that location (e.g. filewall)

Before running any of the other samples, you will need to resolve the issue
and then run CreateDBDDL which creates all the data used in the other sample
applications.

Please let me know if you resolve the problem, or if I can be of any more
help.

Good luck!
--
Best regards

Steve

"Stephane Perron" <misterz at videotron dott ca> wrote in message
news:B065397A-0AD9-44F7-ACAF-17B59175DAE4@news.elevatesoft.com...
> Hi,
>
> So you are THE Steve Forbes.
>
> I've noticed that some of the demos have the ConfigPath property of their
> TEDBEngine component pointing to "C:\Documents and Settings\steveforbes"
> and the TempTablesPath property of the same component pointing to
> "C:\DOCUME~1\STEVEF~2\LOCALS~1\Temp\". Obviously, these paths don't exist
> on my machine. I've tried to change them to a valid one (so I think) but
> it didn't help.
>
> All the demos with that ConfigPath value throw the exception. It might be
> linked to the problem.
>
> I didn't have time (yet) to look at the code and check if those properties
> are changed when the program runs.
>
> The working demos have the ConfigPath property pointing to c:\demos\data,
> which is also invalid on my machine. The TempTablesPath also points to
> "C:\DOCUME~1\STEVEF~2\LOCALS~1\Temp\". Still, those demos work fine.
>
> BTW, the CreateDBDDL sample also throws the exception so I cannot run it.
>
> I'm still working on the problem. I will look at the code itself. It's a
> good way to learn more about EDB...   
>
> Regards,
>
> Stephane
>
>
> "Steve Forbes" <ozmosys@spamfreeoptusnet.com.au> wrote in message
> news:76DC32D1-6AD6-42B2-A5F6-A87C1BAD6A78@news.elevatesoft.com...
>> Hi Guys,
>>
>> I wrote all the sample applications (except for CD collector), and tested
>> them extensively before handing over to Tim, but you've obviously
>> stumbled on something that slipped by First of all, you don't
>> mention it, but have you run the CreateDBDDL sample? I assume you have.
>> This creates the datafolder and DB. If you haven't, this could be the
>> cause of your problem. The demos you mention are table based and
>> therefore would not cause any temporary tables to be created. When each
>> of the applications start, the temporary folder is set to the data
>> location (coz I know this should exists, and it makes the apps generic) I
>> am guessing that there might be a rights issue for that folder, or the
>> folder does not yet exist.
>>
>> --
>> Best regards
>>
>> Steve
>>
>> "Stephane Perron" <misterz at videotron dott ca> wrote in message
>> news:D02DCFE5-B1B6-482E-9048-B0DF4FCB5C05@news.elevatesoft.com...
>>>I installed the trial for EDB and most (but not all) of the demos throw
>>>the same exception "Project xxx.exe raised exception class EEDBException
>>>with message 'ElevateDB Error #406 Invalid temporary table identifier'
>>>when I try to run them.
>>>
>>> the following demos work:
>>>
>>> - GUID
>>> - jpegBlob
>>> - masterdetail
>>> - simpletable
>>> - triggers
>>>
>>> all other demos throw the same exception #406 (including the CD
>>> collector demo)
>>>
>>> I did not test the simplequery demo
>>>
>>> running D7.1 under XP SP2
>>>
>>> - Stephane
>>>
>>>
>>>
>>>
>>>
>>
>>
>
>

Hi,

You probably missed my previous post (correction)

The Createdbddl sample will create a batch of files in the data folder then
will throw the #406 exception. It also throws the exception if I click the
Delete Tables button after running the demo again.

Stephane


"Steve Forbes" <ozmosys@spamfreeoptusnet.com.au> wrote in message
news:79DE2AAE-52D9-46D1-8CA5-90A8A450EE46@news.elevatesoft.com...
> Hi Stephane,
>
>> So you are THE Steve Forbes.
>
> Yep, that's me .. I'm a virus distibuted with the ElevateDB product
> <bg>
>
> The problem with the ConfigPath value is related to the Delphi problem of
> not being able to stream blank string property values. I tried to empty
> the ConfigPath and TempTablesPath for all samples, but the "personalised"
> setting automagically reappeared. Incidentally, Tim said he is going to
> rewrite the component streaming for these two properties so they behave as
> expected. I am sure you will agree, the current situation looks messy.
>
> Both ConfigPath and TempTablesPath are assigned at runtime in the base
> form's FormCreate (see DemoFormBase.pas in the Common folder) to get
> around the problem.
>
> I would suggest first checking to see if there is a Data folder under the
> demos folder coz this is where the data, and the temporary files will be
> located. If there is, I would then check that nothing is blocking the
> creation of files in that location (e.g. filewall)
>
> Before running any of the other samples, you will need to resolve the
> issue and then run CreateDBDDL which creates all the data used in the
> other sample applications.
>
> Please let me know if you resolve the problem, or if I can be of any more
> help.
>
> Good luck!
> --
> Best regards
>
> Steve
>
> "Stephane Perron" <misterz at videotron dott ca> wrote in message
> news:B065397A-0AD9-44F7-ACAF-17B59175DAE4@news.elevatesoft.com...
>> Hi,
>>
>> So you are THE Steve Forbes.
>>
>> I've noticed that some of the demos have the ConfigPath property of their
>> TEDBEngine component pointing to "C:\Documents and Settings\steveforbes"
>> and the TempTablesPath property of the same component pointing to
>> "C:\DOCUME~1\STEVEF~2\LOCALS~1\Temp\". Obviously, these paths don't exist
>> on my machine. I've tried to change them to a valid one (so I think) but
>> it didn't help.
>>
>> All the demos with that ConfigPath value throw the exception. It might be
>> linked to the problem.
>>
>> I didn't have time (yet) to look at the code and check if those
>> properties are changed when the program runs.
>>
>> The working demos have the ConfigPath property pointing to c:\demos\data,
>> which is also invalid on my machine. The TempTablesPath also points to
>> "C:\DOCUME~1\STEVEF~2\LOCALS~1\Temp\". Still, those demos work fine.
>>
>> BTW, the CreateDBDDL sample also throws the exception so I cannot run it.
>>
>> I'm still working on the problem. I will look at the code itself. It's a
>> good way to learn more about EDB...   
>>
>> Regards,
>>
>> Stephane
>>
>>
>> "Steve Forbes" <ozmosys@spamfreeoptusnet.com.au> wrote in message
>> news:76DC32D1-6AD6-42B2-A5F6-A87C1BAD6A78@news.elevatesoft.com...
>>> Hi Guys,
>>>
>>> I wrote all the sample applications (except for CD collector), and
>>> tested them extensively before handing over to Tim, but you've obviously
>>> stumbled on something that slipped by First of all, you don't
>>> mention it, but have you run the CreateDBDDL sample? I assume you have.
>>> This creates the datafolder and DB. If you haven't, this could be the
>>> cause of your problem. The demos you mention are table based and
>>> therefore would not cause any temporary tables to be created. When each
>>> of the applications start, the temporary folder is set to the data
>>> location (coz I know this should exists, and it makes the apps generic)
>>> I am guessing that there might be a rights issue for that folder, or the
>>> folder does not yet exist.
>>>
>>> --
>>> Best regards
>>>
>>> Steve
>>>
>>> "Stephane Perron" <misterz at videotron dott ca> wrote in message
>>> news:D02DCFE5-B1B6-482E-9048-B0DF4FCB5C05@news.elevatesoft.com...
>>>>I installed the trial for EDB and most (but not all) of the demos throw
>>>>the same exception "Project xxx.exe raised exception class EEDBException
>>>>with message 'ElevateDB Error #406 Invalid temporary table identifier'
>>>>when I try to run them.
>>>>
>>>> the following demos work:
>>>>
>>>> - GUID
>>>> - jpegBlob
>>>> - masterdetail
>>>> - simpletable
>>>> - triggers
>>>>
>>>> all other demos throw the same exception #406 (including the CD
>>>> collector demo)
>>>>
>>>> I did not test the simplequery demo
>>>>
>>>> running D7.1 under XP SP2
>>>>
>>>> - Stephane
>>>>
>>>>
>>>>
>>>>
>>>>
>>>
>>>
>>
>>
>
>

Hi Stephane,

Can you step through the code in your debugger and let me know the line
number which throws the #406, or otherwise let me know which of the
following table don't exists after CreateDBDDL

ActiveRecord
ArchivedRecord
AuditLog
Contact
ContactPhone
Customer
GUIDS
Images
Slave
Master
Orders
PhoneType
Triggers

If these all exist open EDBManager set the config path to the samples data
folder and check whether the

- Triggers table has AFTER_INSERT, AFTER_DELETE, and BEFORE_UPDATE tiggers
- Active Record has data in it
- Contact, ContactPhone, and PhoneType have data in them
- Customer and Orders have data in them
- Images has data in it (including images in the BLOB column)
- there are 2 views VIEW_CONTACTPHONELIST and VIEW_CUSTOMERORDERS
- there are 2 procedure PROC_ARCHIVE and PROC_RESTORE

--
Best regards

Steve

"Stephane Perron" <misterz at videotron dott ca> wrote in message
news:F0734EDA-3A77-443A-9348-467297F6FE0D@news.elevatesoft.com...
> Hi,
>
> You probably missed my previous post (correction)
>
> The Createdbddl sample will create a batch of files in the data folder
> then
> will throw the #406 exception. It also throws the exception if I click the
> Delete Tables button after running the demo again.
>
> Stephane
>
>
> "Steve Forbes" <ozmosys@spamfreeoptusnet.com.au> wrote in message
> news:79DE2AAE-52D9-46D1-8CA5-90A8A450EE46@news.elevatesoft.com...
>> Hi Stephane,
>>
>>> So you are THE Steve Forbes.
>>
>> Yep, that's me .. I'm a virus distibuted with the ElevateDB product
>> <bg>
>>
>> The problem with the ConfigPath value is related to the Delphi problem of
>> not being able to stream blank string property values. I tried to empty
>> the ConfigPath and TempTablesPath for all samples, but the "personalised"
>> setting automagically reappeared. Incidentally, Tim said he is going to
>> rewrite the component streaming for these two properties so they behave
>> as expected. I am sure you will agree, the current situation looks messy.
>>
>> Both ConfigPath and TempTablesPath are assigned at runtime in the base
>> form's FormCreate (see DemoFormBase.pas in the Common folder) to get
>> around the problem.
>>
>> I would suggest first checking to see if there is a Data folder under the
>> demos folder coz this is where the data, and the temporary files will be
>> located. If there is, I would then check that nothing is blocking the
>> creation of files in that location (e.g. filewall)
>>
>> Before running any of the other samples, you will need to resolve the
>> issue and then run CreateDBDDL which creates all the data used in the
>> other sample applications.
>>
>> Please let me know if you resolve the problem, or if I can be of any more
>> help.
>>
>> Good luck!
>> --
>> Best regards
>>
>> Steve
>>
>> "Stephane Perron" <misterz at videotron dott ca> wrote in message
>> news:B065397A-0AD9-44F7-ACAF-17B59175DAE4@news.elevatesoft.com...
>>> Hi,
>>>
>>> So you are THE Steve Forbes.
>>>
>>> I've noticed that some of the demos have the ConfigPath property of
>>> their TEDBEngine component pointing to "C:\Documents and
>>> Settings\steveforbes" and the TempTablesPath property of the same
>>> component pointing to "C:\DOCUME~1\STEVEF~2\LOCALS~1\Temp\". Obviously,
>>> these paths don't exist on my machine. I've tried to change them to a
>>> valid one (so I think) but it didn't help.
>>>
>>> All the demos with that ConfigPath value throw the exception. It might
>>> be linked to the problem.
>>>
>>> I didn't have time (yet) to look at the code and check if those
>>> properties are changed when the program runs.
>>>
>>> The working demos have the ConfigPath property pointing to
>>> c:\demos\data, which is also invalid on my machine. The TempTablesPath
>>> also points to "C:\DOCUME~1\STEVEF~2\LOCALS~1\Temp\". Still, those demos
>>> work fine.
>>>
>>> BTW, the CreateDBDDL sample also throws the exception so I cannot run
>>> it.
>>>
>>> I'm still working on the problem. I will look at the code itself. It's a
>>> good way to learn more about EDB...   
>>>
>>> Regards,
>>>
>>> Stephane
>>>
>>>
>>> "Steve Forbes" <ozmosys@spamfreeoptusnet.com.au> wrote in message
>>> news:76DC32D1-6AD6-42B2-A5F6-A87C1BAD6A78@news.elevatesoft.com...
>>>> Hi Guys,
>>>>
>>>> I wrote all the sample applications (except for CD collector), and
>>>> tested them extensively before handing over to Tim, but you've
>>>> obviously stumbled on something that slipped by First of all, you
>>>> don't mention it, but have you run the CreateDBDDL sample? I assume you
>>>> have. This creates the datafolder and DB. If you haven't, this could be
>>>> the cause of your problem. The demos you mention are table based and
>>>> therefore would not cause any temporary tables to be created. When each
>>>> of the applications start, the temporary folder is set to the data
>>>> location (coz I know this should exists, and it makes the apps generic)
>>>> I am guessing that there might be a rights issue for that folder, or
>>>> the folder does not yet exist.
>>>>
>>>> --
>>>> Best regards
>>>>
>>>> Steve
>>>>
>>>> "Stephane Perron" <misterz at videotron dott ca> wrote in message
>>>> news:D02DCFE5-B1B6-482E-9048-B0DF4FCB5C05@news.elevatesoft.com...
>>>>>I installed the trial for EDB and most (but not all) of the demos throw
>>>>>the same exception "Project xxx.exe raised exception class
>>>>>EEDBException with message 'ElevateDB Error #406 Invalid temporary
>>>>>table identifier' when I try to run them.
>>>>>
>>>>> the following demos work:
>>>>>
>>>>> - GUID
>>>>> - jpegBlob
>>>>> - masterdetail
>>>>> - simpletable
>>>>> - triggers
>>>>>
>>>>> all other demos throw the same exception #406 (including the CD
>>>>> collector demo)
>>>>>
>>>>> I did not test the simplequery demo
>>>>>
>>>>> running D7.1 under XP SP2
>>>>>
>>>>> - Stephane
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>
>>>>
>>>
>>>
>>
>>
>
>

Steve,

The following tables from your list don't exist after running createdbddl:

- ArchivedRecord
- GUIDS
- Slave
- Master
- Orders

Strangely, they appear to be tables used by the working demos.

Those tables are created when I run their related demo though ( The GUIDS
table will be created if I run the GUID demo). I believe that it's a feature
of EDB, where the database holds the metadata of the tables and creates the
tables if they don't exist (correct me if I'm wrong).

Regards,

Stéphane


"Steve Forbes" <ozmosys@spamfreeoptusnet.com.au> wrote in message
news:0DB496EA-9EE2-4FB2-B396-1BD107F65227@news.elevatesoft.com...
> Hi Stephane,
>
> Can you step through the code in your debugger and let me know the line
> number which throws the #406, or otherwise let me know which of the
> following table don't exists after CreateDBDDL
>
> ActiveRecord
> ArchivedRecord
> AuditLog
> Contact
> ContactPhone
> Customer
> GUIDS
> Images
> Slave
> Master
> Orders
> PhoneType
> Triggers
>
> If these all exist open EDBManager set the config path to the samples data
> folder and check whether the
>
> - Triggers table has AFTER_INSERT, AFTER_DELETE, and BEFORE_UPDATE tiggers
> - Active Record has data in it
> - Contact, ContactPhone, and PhoneType have data in them
> - Customer and Orders have data in them
> - Images has data in it (including images in the BLOB column)
> - there are 2 views VIEW_CONTACTPHONELIST and VIEW_CUSTOMERORDERS
> - there are 2 procedure PROC_ARCHIVE and PROC_RESTORE
>
> --
> Best regards
>
> Steve
>
> "Stephane Perron" <misterz at videotron dott ca> wrote in message
> news:F0734EDA-3A77-443A-9348-467297F6FE0D@news.elevatesoft.com...
>> Hi,
>>
>> You probably missed my previous post (correction)
>>
>> The Createdbddl sample will create a batch of files in the data folder
>> then
>> will throw the #406 exception. It also throws the exception if I click
>> the
>> Delete Tables button after running the demo again.
>>
>> Stephane
>>
>>
>> "Steve Forbes" <ozmosys@spamfreeoptusnet.com.au> wrote in message
>> news:79DE2AAE-52D9-46D1-8CA5-90A8A450EE46@news.elevatesoft.com...
>>> Hi Stephane,
>>>
>>>> So you are THE Steve Forbes.
>>>
>>> Yep, that's me .. I'm a virus distibuted with the ElevateDB product
>>> <bg>
>>>
>>> The problem with the ConfigPath value is related to the Delphi problem
>>> of not being able to stream blank string property values. I tried to
>>> empty the ConfigPath and TempTablesPath for all samples, but the
>>> "personalised" setting automagically reappeared. Incidentally, Tim said
>>> he is going to rewrite the component streaming for these two properties
>>> so they behave as expected. I am sure you will agree, the current
>>> situation looks messy.
>>>
>>> Both ConfigPath and TempTablesPath are assigned at runtime in the base
>>> form's FormCreate (see DemoFormBase.pas in the Common folder) to get
>>> around the problem.
>>>
>>> I would suggest first checking to see if there is a Data folder under
>>> the demos folder coz this is where the data, and the temporary files
>>> will be located. If there is, I would then check that nothing is
>>> blocking the creation of files in that location (e.g. filewall)
>>>
>>> Before running any of the other samples, you will need to resolve the
>>> issue and then run CreateDBDDL which creates all the data used in the
>>> other sample applications.
>>>
>>> Please let me know if you resolve the problem, or if I can be of any
>>> more help.
>>>
>>> Good luck!
>>> --
>>> Best regards
>>>
>>> Steve
>>>
>>> "Stephane Perron" <misterz at videotron dott ca> wrote in message
>>> news:B065397A-0AD9-44F7-ACAF-17B59175DAE4@news.elevatesoft.com...
>>>> Hi,
>>>>
>>>> So you are THE Steve Forbes.
>>>>
>>>> I've noticed that some of the demos have the ConfigPath property of
>>>> their TEDBEngine component pointing to "C:\Documents and
>>>> Settings\steveforbes" and the TempTablesPath property of the same
>>>> component pointing to "C:\DOCUME~1\STEVEF~2\LOCALS~1\Temp\". Obviously,
>>>> these paths don't exist on my machine. I've tried to change them to a
>>>> valid one (so I think) but it didn't help.
>>>>
>>>> All the demos with that ConfigPath value throw the exception. It might
>>>> be linked to the problem.
>>>>
>>>> I didn't have time (yet) to look at the code and check if those
>>>> properties are changed when the program runs.
>>>>
>>>> The working demos have the ConfigPath property pointing to
>>>> c:\demos\data, which is also invalid on my machine. The TempTablesPath
>>>> also points to "C:\DOCUME~1\STEVEF~2\LOCALS~1\Temp\". Still, those
>>>> demos work fine.
>>>>
>>>> BTW, the CreateDBDDL sample also throws the exception so I cannot run
>>>> it.
>>>>
>>>> I'm still working on the problem. I will look at the code itself. It's
>>>> a good way to learn more about EDB...   
>>>>
>>>> Regards,
>>>>
>>>> Stephane
>>>>
>>>>
>>>> "Steve Forbes" <ozmosys@spamfreeoptusnet.com.au> wrote in message
>>>> news:76DC32D1-6AD6-42B2-A5F6-A87C1BAD6A78@news.elevatesoft.com...
>>>>> Hi Guys,
>>>>>
>>>>> I wrote all the sample applications (except for CD collector), and
>>>>> tested them extensively before handing over to Tim, but you've
>>>>> obviously stumbled on something that slipped by First of all, you
>>>>> don't mention it, but have you run the CreateDBDDL sample? I assume
>>>>> you have. This creates the datafolder and DB. If you haven't, this
>>>>> could be the cause of your problem. The demos you mention are table
>>>>> based and therefore would not cause any temporary tables to be
>>>>> created. When each of the applications start, the temporary folder is
>>>>> set to the data location (coz I know this should exists, and it makes
>>>>> the apps generic) I am guessing that there might be a rights issue for
>>>>> that folder, or the folder does not yet exist.
>>>>>
>>>>> --
>>>>> Best regards
>>>>>
>>>>> Steve
>>>>>
>>>>> "Stephane Perron" <misterz at videotron dott ca> wrote in message
>>>>> news:D02DCFE5-B1B6-482E-9048-B0DF4FCB5C05@news.elevatesoft.com...
>>>>>>I installed the trial for EDB and most (but not all) of the demos
>>>>>>throw the same exception "Project xxx.exe raised exception class
>>>>>>EEDBException with message 'ElevateDB Error #406 Invalid temporary
>>>>>>table identifier' when I try to run them.
>>>>>>
>>>>>> the following demos work:
>>>>>>
>>>>>> - GUID
>>>>>> - jpegBlob
>>>>>> - masterdetail
>>>>>> - simpletable
>>>>>> - triggers
>>>>>>
>>>>>> all other demos throw the same exception #406 (including the CD
>>>>>> collector demo)
>>>>>>
>>>>>> I did not test the simplequery demo
>>>>>>
>>>>>> running D7.1 under XP SP2
>>>>>>
>>>>>> - Stephane
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>
>>>>>
>>>>
>>>>
>>>
>>>
>>
>>
>
>

Hi Stephane,

> table will be created if I run the GUID demo). I believe that it's a
> feature of EDB, where the database holds the metadata of the tables and
> creates the tables if they don't exist (correct me if I'm wrong).

Yes, you are absolutely correct. My mistake

What about the other metadata items mentioned in my previous post (viewed
via EDBManager)?

If you have a chance to step through the code in the debugger we can
probably isolate the problem quite quickly.

--
Best regards

Steve

"Stephane Perron" <misterz at videotron dott ca> wrote in message
news:84EC86E3-D12A-4D2C-A512-40AAF07AC7AA@news.elevatesoft.com...
> Steve,
>
> The following tables from your list don't exist after running createdbddl:
>
> - ArchivedRecord
> - GUIDS
> - Slave
> - Master
> - Orders
>
> Strangely, they appear to be tables used by the working demos.
>
> Those tables are created when I run their related demo though ( The GUIDS
> table will be created if I run the GUID demo). I believe that it's a
> feature of EDB, where the database holds the metadata of the tables and
> creates the tables if they don't exist (correct me if I'm wrong).
>
> Regards,
>
> Stéphane