I'm looking at EDB and compiled the CreateDBDLL demo but when I run it I get
the following error how do I correct this so all of the tables will be
created?

Thanks,
 Don

Don


Just tried running it here and its fine. Can you supply a bit more information about the version of ElevateDB and the IDE you're trying.

Roy Lambert [Team Elevate]

Roy,

 EDB 2.04.2, D5 & D7, Win XP sp3., 6 tables are created Contacts,
ContactPhone, PhoneType, GUIDS, Orders and Triggers all contain some data
except the GUIDS & Triggers tables. Doesn't appear all of the tables are
being created.

Don

"Roy Lambert" <roy.lambert@skynet.co.uk> wrote in message
news:B51F73BD-ABAD-4DD5-BDED-88D0DF69AD2C@news.elevatesoft.com...
> Don
>
>
> Just tried running it here and its fine. Can you supply a bit more
> information about the version of ElevateDB and the IDE you're trying.
>
> Roy Lambert [Team Elevate]
>

Don


Unfortunately I haven't installed 2.04 yet so I'm not sure. It may just be that the sql in the demos needs updating for the changes in 2.04, but as you say there are a number of tables that aren't being created (at least if your list is all you have). I shall not be installing 2.04 for a while yet (in the middle of to much to add another variable) so I'm sorry I can't help.

Roy Lambert [Team Elevate]

<<
I'm looking at EDB and compiled the CreateDBDLL demo but when I run it I get
the following error how do I correct this so all of the tables will be
created?
>>

Confirmed - looks like 2.04b2 broke the samples.

The (first) exception is in creating a trigger in "CreateTriggersSampleTables" function.

Specifically this:
       SQL.Add('CREATE TRIGGER "AFTER_INSERT" AFTER INSERT ON "Triggers"');
       SQL.Add('BEGIN');
       SQL.Add('  DECLARE TriggerCursor SENSITIVE CURSOR FOR TriggerStatement;');
       SQL.Add('');
       SQL.Add('  PREPARE TriggerStatement FROM ''SELECT * FROM AuditLog'';');
       SQL.Add('  OPEN TriggerCursor;');
       SQL.Add('');
       SQL.Add('  INSERT INTO TriggerCursor (EventType, TableName, RecordId, NewValue)');
       SQL.Add('    VALUES (1, ''TRIGGERS'', NEWROW.Id, NEWROW.Name);');
       SQL.Add('END');
       ExecSQL;


Raul

Raul


What happens if you quote the column names?

Roy Lambert

Don,

> I'm looking at EDB and compiled the CreateDBDLL demo but when I run it I
> get
> the following error how do I correct this so all of the tables will be
> created?

Looks like the demo source was not updated to accomodate the changes to 2.04
which allows for variables for table and field names within scripts,
procedures, and functions.

To get past the first exception locate the insert statements and add two
single quotes before and after each field name.  So

     SQL.Add('  INSERT INTO TriggerCursor (EventType, TableName, RecordId,
NewValue)');

changs to

      SQL.Add('  INSERT INTO TriggerCursor (''EventType'', ''TableName'',
''RecordId'', ''NewValue'')');



Then add two single quotes before and after each table name in the start
tranasaction call that is in the procedure create steps.  So


     SQL.Add('START TRANSACTION ON TABLES ActiveRecord, ArchivedRecord;');

changs to

     SQL.Add('START TRANSACTION ON TABLES ''ActiveRecord'',
''ArchivedRecord'';');



--

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

Now shipping Atrex 13.  For more information go to
 http://www.atrex.com/news.asp

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

<<

"Terry Swiers" wrote:

      SQL.Add('  INSERT INTO TriggerCursor (''EventType'', ''TableName'',
''RecordId'', ''NewValue'')');
>>

There were 3 of these


<<
     SQL.Add('START TRANSACTION ON TABLES ''ActiveRecord'',
''ArchivedRecord'';');

>>

and 2 of these and then it compiled and ran OK.

Thanks,
Raul

Thanks Terry really appreciate the help.

 Don

"Terry Swiers" <millennium@1000years.com> wrote in message
news:C9A61464-F860-4DD0-B8E1-F1E5E087B47F@news.elevatesoft.com...
> Don,
>
>> I'm looking at EDB and compiled the CreateDBDLL demo but when I run it I
>> get
>> the following error how do I correct this so all of the tables will be
>> created?
>
> Looks like the demo source was not updated to accomodate the changes to
> 2.04 which allows for variables for table and field names within scripts,
> procedures, and functions.
>
> To get past the first exception locate the insert statements and add two
> single quotes before and after each field name.  So
>
>      SQL.Add('  INSERT INTO TriggerCursor (EventType, TableName, RecordId,
> NewValue)');
>
> changs to
>
>       SQL.Add('  INSERT INTO TriggerCursor (''EventType'', ''TableName'',
> ''RecordId'', ''NewValue'')');
>
>
>
> Then add two single quotes before and after each table name in the start
> tranasaction call that is in the procedure create steps.  So
>
>
>      SQL.Add('START TRANSACTION ON TABLES ActiveRecord, ArchivedRecord;');
>
> changs to
>
>      SQL.Add('START TRANSACTION ON TABLES ''ActiveRecord'',
> ''ArchivedRecord'';');
>
>
>
> --
>
> ---------------------------------------
>  Terry Swiers
>  Millennium Software, Inc.
>  http://www.1000years.com
>  http://www.atrex.com
>
> Now shipping Atrex 13.  For more information go to
>  http://www.atrex.com/news.asp
>
> 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)
>  ---------------------------------------
>
>
>

Terry


That's what I was trying to remember. I was slightly baffled though since I was thinking this is an sql statement not a script, function or procedure.

Roy Lambert