This is with EDB 2.03 build 4--

I create a table with a couple of fields, one of them Varbyte of size 4.
  I open the table and tab to the varbyte field.  Not knowing what data
format it expects, I type in 0070F0B0 and press tab.  Error:

Access violation at address 004031E3 in module 'edbmgr.exe'. Read of
address 00134829.

If I click back into the varbyte field, the same error message appears
in a loop and the program must be killed.

Charles


From the OLH

Binary literals use the 'X' character along with the single quote (') character to identify themselves as such. The contents of a binary literal consists of the bytes that make up the value encoded in hexadecimal form, such that each byte is represented by two characters from the range of '00' (0) to 'FF' (255).

so try X'004031E3

Roy Lambert

Roy Lambert wrote:
> Charles
>
>
> From the OLH
>
> Binary literals use the 'X' character along with the single quote (') character to identify themselves as such. The contents of a binary literal consists of the bytes that make up the value encoded in hexadecimal form, such that each byte is represented by two characters from the range of '00' (0) to 'FF' (255).
>
> so try X'004031E3
>
> Roy Lambert
>

The EDB Manager data entry grid rejects that format (I expect it is
meant for SQL statements only), but at least gives a sensible and
dismissable error message.

Some strings of hex digits are accepted without any reported error, but
produce weird data dumps in the Column Details view.  Example, 44556677
 produces a dump beginning with "66770000" and going on for 21,828
bytes.  Hmm, 21828 = $5544, so it seems the first 2 bytes are being
interpreted as a length even though the field is defined as 4 bytes long.

P.S to Tim--I decided that varbytes weren't what I wanted anyway, so I'm
not pressing for a quick fix.

Charles


I just created a memory table to have a go, typed 12 into the field and it seemed OK. The display was nothing I would have guessed (000000A0361F0390B95D0001000000010000). However I also notice that the display is different for when the row is selected, in data entry mode or simply sitting there. The value I've show in the data input one. Please don't ask me to type the others.

Type 1 or 123 into a field and you get
---------------------------
ElevateDB Manager
---------------------------
Invalid SQL-formatted binary string.
---------------------------
OK  
---------------------------

1234 is freaky. First you loose your cursor then  you get a freaked out display (as you mentioned) then you have to bomb EDBManager.

I think its likely that its an EDBManager problem

Roy Lambert

Charles,

<< I create a table with a couple of fields, one of them Varbyte of size 4.
I open the table and tab to the varbyte field.  Not knowing what data format
it expects, I type in 0070F0B0 and press tab.  Error:

Access violation at address 004031E3 in module 'edbmgr.exe'. Read of
address 00134829.

If I click back into the varbyte field, the same error message appears in a
loop and the program must be killed. >>

I'll check it out and make sure that this is fixed.  The BYTE/VARBYTE
handling in Delphi is a bit wonky, so we have to jump through some hoops to
get it to work correctly.

--
Tim Young
Elevate Software
www.elevatesoft.com