First time playing with ElevateDB.

I have been able to get the tables up and running and displaying data ok.

One table contains many extraneous records and I want to delete all the records that don't match a certain criteria. I have added a query to the form with the following SQL:

DELETE FROM tblFred
WHERE fEvent <> 'Script'

When I try to make the Query active I get an 'Error creating table handle' error.

I have put some other simple SQL statements in and have been able to make the query active but the above always fails.

Any help appreciated.

I should add that the SQL executes correctly in the EDBManager

John

>When I try to make the Query active I get an 'Error creating table handle' error.
>
>I have put some other simple SQL statements in and have been able to make the query active but the above always fails.

There's nothing different about this type of query than any other. What happens if you simply replace the sql in a query that you know works with the code in this one?

Roy Lambert [Team Elevate]

John,

> When I try to make the Query active I get an 'Error creating table handle'
> error.

Assuming that you are doing this from inside your code, make sure that you
are calling ExecSQL rather than calling Open or setting Active := True.
Since this doesn't return a result set, you really can't make it Active.

--

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

John,

<< When I try to make the Query active I get an 'Error creating table
handle' error. >>

Terry is correct - ExecSQL for anything that doesn't return a result set,
although with EDB you can just use ExecSQL for everything, including SELECT
statements, since EDB extends the expected ExecSQL behavior to include
automatically opening up any result sets that are returned.

--
Tim Young
Elevate Software
www.elevatesoft.com

Used only ExecSQL. All good.

Thanks

John