Using OI32 4.0.1, having problems with edit table "SELPOS".

Is it possible to upgrade the datatbl.dll only without upgrading anything else? My datatbl.dll is 122,368 02/06/2002. If so where would I find the upgrade?

I have the 4.1 and 4.1.2 upgrades, I just do not want to upgrade at this time. The zip files have "CAB" files in them, and I would guess that the only way to extract information is to do the whole upgrade. Yes?

The latest version of WinZip will extract one or more files from .CAB files. I also think you can do it with a standard Windows utility .. just don't remember which and too lazy to look right now. But it CAN be done.

Don M.

Richard,

I *know* you don't want to upgrade at this time but if memory serves 4.0.1 might have been a little flakey. 4.0.3 would be a better upgrade if you don't want to go all the way to 4.1.2 (which is my best recommendation).

[email protected]

SRP Computer Solutions, Inc.

Richard,

What kind of problems with SELPOS?

Never mind if you're sure they can't be circumvented.

- Oystein -

Ohhhhh neverrrrr minddddd!!! I just can't believe I do these things. A statement… ROW += 1 just did me in!

I was using the following statements to unselect a row.

ET_FOCUS=@WINDOW:'.SELECTION'

HANDLE=GET_PROPERTY(ET_FOCUS,'HANDLE')

RESULT=SENDMESSAGE(HANDLE,1085,0,0)

Since my edit table is single select, the above way does not work! This way works.

ET_FOCUS=@WINDOW:'.SELECTION'

HANDLE=GET_PROPERTY(ET_FOCUS,'HANDLE')

ROW=SENDMESSAGE(HANDLE,1115,0,0)

RESULT=SENDMESSAGE(HANDLE,1083,0,ROW)

Note that the third argument, when 0 deselects, and when 1 selects.

And what caused me to overlook a long ago post from Don, was the fact that when I was getting the "ROW", I added 1 to it. Since I was using the row for other "non" "sendmessage" functions I had to add 1 to it.

Geeessss, I spent hours on this. I even did a work around that got the edit table "array" and then set the "array". I just did not like it because the edit table could have alot of rows. And since every other row is contrasted colored, I also had to set the color of every other row again.

Ok, all is fine now.

Richard,

Since I was using the row for other "non" "sendmessage" functions I had to add 1 to it.

Or you could simply have had two variables instead of one, like CurrentRow and NextRow, with NextRow=CurrentRow + 1. Variables are cheap.

- Oystein -

PS. Just gearing up to start teaching at the 101 programming course again.

Sure could have. Remember that I did have a brain freeze. The killer is that it took me hours to figure the "ROW += 1" error. It was a "left over" statement.

I am now getting a good laugh about it. Although yesterday, I was about to throw things. :o)

View this thread on the Works forum...