Hello

I open a Table on the edbManager and try to delete a record
After the confirmation either I get the error #700 or on other cases the
edbmanager stuck completly.

I try to verify and repair the table but it doesn't help.
Beside the delete all others operation run ok.

I guess that I'll have to upload the database.
Since it is quite a large database are there any suggestions to make it more
effcient?

I use ver 2.05b7

Thanks
Sorin

Sorin


Reading the manual

EDB_ERROR_COMPILE (700) An error was found in the <ObjectType> at line <Line>
and column <Column> (<ErrorMessage>)This error is
raised whenever an error is encountered while
compiling an SQL expression, statement, or routine.
The specific error message is indicated within the
parentheses.

That suggests to me you have a trigger (before or after delete) which is screwing up.


<<Since it is quite a large database are there any suggestions to make it more
effcient?>>

In what way? You'll need to be a lot more specific if you don't want an answer like "create all the necessary indices"

Roy Lambert [Team Elevate]

Roy,

> <<Since it is quite a large database are there any suggestions to make it more
> effcient?>>

I think, he means, if it's necessary to upload the whole database.

Regards Uli

Uli

>> <<Since it is quite a large database are there any suggestions to make it more
>> effcient?>>
>
>I think, he means, if it's necessary to upload the whole database.

errr in that case why is he asking us? We can't help with upload speed.

Roy Lambert

Roy,

> errr in that case why is he asking us? We can't help with upload speed.

True.

Uli

I guess he means "how can I pull out just this problem table to send", so he doesn't have to upload the whole thing.

My suggestion would be:

1. Create a new database in EDBMgr, within the same session as the existing problem database.

2. Click on this DB to select it. Create a new SQL Statement.

3. Select the table with the problem with the mouse & drag its contents into the NEW.SQL. Click yes when asked to include data.

4 Run this query.

... now you have your problem table in its own database.

* Does it still have the problem??
  -> If not then some other procedure or function from the existing database is causing the problem ...

* Repeat steps 1 - 4 with all the procedures or functions which include this table until you get the error message!

--

The thing is that you can change stuff in a DB (i.e. fields in a table) and the impact is only evident when you trigger a a particular procedure which references some field you have removed.

> That suggests to me you have a trigger (before or after delete) which is
> screwing up.

Yes the problem is on a called procedure after delete.

I'll work on it and try to fix it.

Thanks
Sorin

Ok

Half problem solved.
I fix the after delete called procedure but the cases when edbmanager
completly stuck still continue.

I found that the statement "SELECT Id FROM Table1, Table2, Table3 WHERE
MainId = SomeValue"
run well when the result is empty but stuck when the result isn't empty.

What I'm missing now?

Thanks
Sorin

Sorin


>Half problem solved.
>I fix the after delete called procedure but the cases when edbmanager
>completly stuck still continue.
>
>I found that the statement "SELECT Id FROM Table1, Table2, Table3 WHERE
>MainId = SomeValue"
>run well when the result is empty but stuck when the result isn't empty.
>
>What I'm missing now?

It depends on the sizes of the tables. You could be generating a MASSIVE result set or intermediate result set with that syntax. What are you trying to achieve?

Roy Lambert [Team Elevate]

> It depends on the sizes of the tables. You could be generating a MASSIVE
> result set or intermediate result set with that syntax. What are you
> trying to achieve?

I use the statement ""SELECT Id FROM Table1, Table2, Table3 WHERE MainId =
SomeValue"
to check if the the "SomeValue" exist on any of the tables.

Yes the result can be big some times but I wait for more then 40 minutes and
the edbmenager don't show any result.
I have to use the task menager to close it

Thanks
Sorin