Icon View Thread

The following is the text of the current message along with any replies.
Messages 1 to 7 of 7 total
Thread EDB 2.02b11 Error
Fri, Apr 10 2009 1:29 PMPermanent Link

Greg Bishop
I just upgraded to ElevateDB 2.02b11 from 2.02b7 (both Unicode within Delphi 2009 Pro).  When executing my compiled EXE, I get the following
error when opening a TEDBQuery:

    ElevateDB Error #100 There is an error in the metadata for the index __Distinct (The index page size is below the required of 9144).

When attempting to open some tables within EDB Manager, I get the following error:

    Access violation at address 005A83F2 in module 'edbmgr.exe'.  Write of address 00000040.

However, I can execute a simple "SELECT * FROM Table" SQL query in EDB Manager using the same tables that gives the errors above when I try
to open them in EDB Manager.

The index page size for all tables in my database is 4096, the default value.  Do I need to go through and update them all to 9144 for some
reason?  The only index that I have on some tables giving these errors is the primary key index.

Any ideas?
Mon, Apr 13 2009 10:30 AMPermanent Link

Tim Young [Elevate Software]

Elevate Software, Inc.

Avatar

Email timyoung@elevatesoft.com

Greg,

Per my reply via email:

The issue with the table opens is with the computed columns.  The nature of
the problem is such that it would only cause an exception under certain
circumstances, thus it was making it past our internal test framework.  It
was basically a "with" scope issue on a particular object member.  Most of
the time the incorrect scope wouldn't result in a problem because the
incorrect object member reference still resulted in a correct value for the
operation in question.

In the newsgroup message, you mentioned a DISTINCT query that was causing an
exception.   Do you have the SQL that is causing the error ?

I'll get a fix out for both of these issues as soon as I figure out what the
query DISTINCT issue is.

--
Tim Young
Elevate Software
www.elevatesoft.com

Tue, Apr 14 2009 2:40 AMPermanent Link

"Greg Bishop"
Tim:

There is no actual DISTINCT query.  DISTINCT was part of the error message
that I was receiving.

The query I'm getting this message from is pasted below.  This is from a
TEDBQuery component within Delphi 2009.

Greg

=====

SELECT AddressID, Description, Address1, Address2, City, State, PostalCode,
Country,
 True AS Primary FROM Address
WHERE (AddressID IN
 (SELECT AddressID FROM ContactToAddress
 WHERE ContactID = :ContactID))
 AND (:PrimaryPhysicalAddressID = AddressID)
UNION
SELECT AddressID, Description, Address1, Address2, City, State, PostalCode,
Country,
 False AS Primary FROM Address
WHERE (AddressID IN
 (SELECT AddressID FROM ContactToAddress
 WHERE ContactID = :ContactID))
 AND (:PrimaryPhysicalAddressID <> AddressID)

=====


"Tim Young [Elevate Software]" <timyoung@elevatesoft.com> wrote in message
news:ACB2569B-A457-452C-803B-F1C66835BDC0@news.elevatesoft.com...
> Greg,
>
> Per my reply via email:
>
> The issue with the table opens is with the computed columns.  The nature
> of
> the problem is such that it would only cause an exception under certain
> circumstances, thus it was making it past our internal test framework.  It
> was basically a "with" scope issue on a particular object member.  Most of
> the time the incorrect scope wouldn't result in a problem because the
> incorrect object member reference still resulted in a correct value for
> the
> operation in question.
>
> In the newsgroup message, you mentioned a DISTINCT query that was causing
> an
> exception.   Do you have the SQL that is causing the error ?
>
> I'll get a fix out for both of these issues as soon as I figure out what
> the
> query DISTINCT issue is.
>
> --
> Tim Young
> Elevate Software
> www.elevatesoft.com
>
>

Tue, Apr 14 2009 8:36 AMPermanent Link

Tim Young [Elevate Software]

Elevate Software, Inc.

Avatar

Email timyoung@elevatesoft.com

Greg,

<< The query I'm getting this message from is pasted below.  This is from a
TEDBQuery component within Delphi 2009. >>

Fanstastic, thanks.  It's now fixed.

--
Tim Young
Elevate Software
www.elevatesoft.com

Wed, Apr 29 2009 1:11 PMPermanent Link

Greg Bishop
Tim:

Thanks for the fix.  Is there any kind of work-around until the next build is released?  ... Such as rebuilding indices, etc.?

Greg Bishop
Wed, Apr 29 2009 2:12 PMPermanent Link

Tim Young [Elevate Software]

Elevate Software, Inc.

Avatar

Email timyoung@elevatesoft.com

Greg,

<< Thanks for the fix.  Is there any kind of work-around until the next
build is released?  ... Such as rebuilding indices, etc.? >>

Not really.  However, B12 is getting prepared now (afternoon EST -5 GMT), so
it should be available by the morning.

--
Tim Young
Elevate Software
www.elevatesoft.com

Wed, Apr 29 2009 2:19 PMPermanent Link

Greg Bishop
10-4.  Thanks.
Image