On Dec 8, 2008, at 11:36 AM, Tonny Staunsbrink wrote:
I had a similar problem and was never able to fix it. The solution
was to make the foreign keys visible and create the faults in my own
code.
I have a feeling that it is a bug in handling cross-database
relationships where the destinati
>
> I had a similar problem and was never able to fix it. The solution was to
> make the foreign keys visible and create the faults in my own code.
> I have a feeling that it is a bug in handling cross-database relationships
> where the destination object is part of an inheritance structure. I see
On Dec 3, 2008, at 5:28 PM, Chuck Hill wrote:
I think I will guess that this is a bug. What does the fetch spec
and qualifier look like again?
Ahg. You would ask that.
Well, see, this here is a Direct To Java Client app, so it is making
the fetch automatically, on it's own, based on the
On Dec 2, 2008, at 11:03 AM, David Avendasora wrote:
This is a simple one-attribute PK to FK relationship. No fancy
qualifiers or anything else.
Should this work or no?
Probably? Let's take a look at the error message:
It should. I have a very similar setup working elsewhere in my
a
This is a simple one-attribute PK to FK relationship. No fancy
qualifiers or anything else.
Should this work or no?
Probably? Let's take a look at the error message:
It should. I have a very similar setup working elsewhere in my
application. I knew I wasn't hallucinating, even if that
On Dec 2, 2008, at 9:29 AM, David Avendasora wrote:
Hi,
I just want to make sure I understand the error I'm getting and if
it is to be expected, or if it _should_ work, but I'm messing
something else up.
I have the following relationship:
ExternalLotCode <<-> LotCode
Each entity is in
Hi,
I just want to make sure I understand the error I'm getting and if it
is to be expected, or if it _should_ work, but I'm messing something
else up.
I have the following relationship:
ExternalLotCode <<-> LotCode
Each entity is in a different EOModel, AND in a different Database.
When
