After upgrading from EDB 1 to EDB2 my app gives an error #700 on
running a particular query:

The table or view MyTable does not exist.

The problem sql uses a join between a memory table and a regular
table.

SELECT MT.Field1, T.Field2 FROM MEMORY.MyMemoryTable MT JOIN MyTable T
ON(MT.ID=T.ID)

Has anything changed in v2 in this respect? I don't see anything in
the release notes.

On Mon, 14 Sep 2009 13:27:33 -0700, Michael Fullerton
<fullerm@cybermatrix.com> wrote:

>After upgrading from EDB 1 to EDB2 my app gives an error #700 on
>running a particular query:
>
>The table or view MyTable does not exist.
>
>The problem sql uses a join between a memory table and a regular
>table.
>
>SELECT MT.Field1, T.Field2 FROM MEMORY.MyMemoryTable MT JOIN MyTable T
>ON(MT.ID=T.ID)
>
>Has anything changed in v2 in this respect? I don't see anything in
>the release notes.

OK I understand the problem. The non-memory table needs to have its
database name in front of it too. Why is that? Can this be changed?

Michael,

<< OK I understand the problem. The non-memory table needs to have its
database name in front of it too. Why is that? Can this be changed? >>

It's a bug in 2.02 B15.  It will be fixed in the 2.03 release.

--
Tim Young
Elevate Software
www.elevatesoft.com