Hello

I have the next 2 errors and maybe it will help solve the problem from my
previous thread.

First one
I have Table1 with Id as primarykey and Table2 with the field Field1Id
defined as Foreign Key
to target table Table1 primarykey.
When I try to drop Table2 it raise the error:
"#201 The table Table2 ...cannot be dropped because it is still referenced
by
constraint primarykey in the table Table1"
The reference is on the oposite direction so way this error?

Second one
The same 2 tables are on a datamodule with a datasource attached to Table1.
On Table2 properties I set MasterSource to the datasource the IndexName to
Field1Id and
when I press on the MasterFields it raise the eror
"#700 .. at line 7 and column 10 (Invalid expression ? found, dynamic
parameter reference not allowed)"

I believe that the errors are related.
I'm using ver 2.03b17

Thanks
Sorin

Sorin


Can't help with the first one since I refuse to use RI unless there's a switch to turn it off. The second one reads like an error message from a query. Is this the same database that you're having the other problem with? If so it may be a corrupt catalog. How it would get that way I don't know.

Try this:

1. copy the catalog and database so you have a safe copy somewhere
2. reverse engineer the database with data
3. drop the database
4. create a new version from the reverse enginered one.

Roy Lambert [Team Elevate]

For the first one: constraints must be dropped before either table
mentioned in the constraint can be dropped.  The direction doesn't
matter, it's the fact that they're linked that matters.

I don't believe the two issues are related.

--
David Cornelius
Cornelius Concepts

On 7/30/2010 7:34 AM, Sorin H wrote:
> Hello
>
> I have the next 2 errors and maybe it will help solve the problem from my
> previous thread.
>
> First one
> I have Table1 with Id as primarykey and Table2 with the field Field1Id
> defined as Foreign Key
> to target table Table1 primarykey.
> When I try to drop Table2 it raise the error:
>   "#201 The table Table2 ...cannot be dropped because it is still referenced
> by
> constraint primarykey in the table Table1"
> The reference is on the oposite direction so way this error?
>
> Second one
> The same 2 tables are on a datamodule with a datasource attached to Table1.
> On Table2 properties I set MasterSource to the datasource the IndexName to
> Field1Id and
> when I press on the MasterFields it raise the eror
> "#700 .. at line 7 and column 10 (Invalid expression ? found, dynamic
> parameter reference not allowed)"
>
> I believe that the errors are related.
> I'm using ver 2.03b17
>
> Thanks
> Sorin
>
>

Thanks David

Ok, if that is the rule.
I don't see the logic but probably Tim take into acount things I don't think
about.

Thanks
Sorin


"David Cornelius" <dev@corneliusconcepts.com> wrote in message
> For the first one: constraints must be dropped before either table
> mentioned in the constraint can be dropped.  The direction doesn't matter,
> it's the fact that they're linked that matters.
>
> I don't believe the two issues are related.

"Roy Lambert" <roy.lambert@skynet.co.uk> wrote in message
> Can't help with the first one since I refuse to use RI unless there's a
> switch to turn it off. The second one reads like an error message from a
> query. Is this the same database that you're having the other problem
> with? If so it may be a corrupt catalog. How it would get that way I don't
> know.
>
> Try this:
>
> 1. copy the catalog and database so you have a safe copy somewhere
> 2. reverse engineer the database with data
> 3. drop the database
> 4. create a new version from the reverse enginered one.

From David I understand that first error it's not an error.

The second error ocure between 2 ttables, no query involved.
Yes it is the same database and table from the previous problem.

I couldn't reverse engineer the database with data. After a long proccess
the edbmanager show the error "Out of memory"
and the created script can't be saved or copy.
So I try to reverse engineer without the data and after droping and recreate
the database I run the script,
creates empty tables but the same problem remain.
When I try to open the MasterFields property I get the error"
""#700 .. at line 7 and column 10 (Invalid expression ? found, dynamic
parameter reference not allowed)"

Thanks again for the help
Sorin

Sory, sory!!!
I apologize for bothering
It's a stupid mistake I make and notice only now.

Thanks and apologize again
Sorin

Sorin,

<< I have Table1 with Id as primarykey and Table2 with the field Field1Id
defined as Foreign Key to target table Table1 primarykey.
When I try to drop Table2 it raise the error: "#201 The table Table2
....cannot be dropped because it is still referenced by constraint primarykey
in the table Table1"

The reference is on the oposite direction so way this error? >>

This is just a quirk with how the dependencies work for FK constraints in
EDB, and will hopefully be changed soon.  You have to alter the table that
contains the FK and drop the FK first.  Then you will be able to drop the
table itself.

<< The same 2 tables are on a datamodule with a datasource attached to
Table1. On Table2 properties I set MasterSource to the datasource the
IndexName to Field1Id and when I press on the MasterFields it raise the eror
"#700 .. at line 7 and column 10 (Invalid expression ? found, dynamic
parameter reference not allowed)" >>

What is the entire error message ?  Also, are there any triggers defined for
either of the two tables ?

--
Tim Young
Elevate Software
www.elevatesoft.com

Sorin,

<< I apologize for bothering It's a stupid mistake I make and notice only
now. >>

I need to make sure to read the whole thread before commenting.

--
Tim Young
Elevate Software
www.elevatesoft.com

"Tim Young [Elevate Software]" <timyoung@elevatesoft.com> wrote in message

> What is the entire error message ?  Also, are there any triggers defined
> for either of the two tables ?
>

Here was my error.
The MasterSource was set to the wrong query.

Thanks
Sorin