bb.donnay-software.com

Sometimes "automated" just doesn't cut it and a little programming is required.

Rick Dalzell's solution looks pretty "slick" to me.

DC_SetRelation() is basically a wrapper function that uses dbSetRelation().
This performs a seek based on the currently selected order of the relational database.
Why do you want to select a different index tag than the one needed for the seek?

The below code is from _DCXBROW.PRG. I don't see anything wrong with it. I used this in an application where I used SqlExpress. ELSEIF aGetListItem[nGETLIST_SUBTYPE] = BROWSE_SQLEXPRESS // SQLExpress browse ::skipBlock := {|n,o| o:dataSource:Skipper(n) } ::goTopBlock := {|o| o:dataSource:goTop() } :...

If you show me your workaround, I will add it to eXpress++ build 255.

Tom -

Are you saying that you have found a workaround or do you still need help from me?

Roger

The /c option is asking to open up a command shell. This may be due to the non-support of DOS programs under Windows 7.

The multiple flickering is being caused by the following line of code: PREEVAL {|o|o:clipSiblings := .f.} Comment out this line. I noticed that the flickering was caused only when clicking on a tab to the "left" of the currently selected tab. That's what led me to believe it was something about the ...

I didn't completely read your postings.
I thought you were using colored tabpages.

Now I see that you are using simulated tabpages.

I will see what I can do.

Tom -

I have been working on the eXpress++ resizing system this week while in Terry Wolfe's office. I agree that the DC_CompleteEvents() call can interfere with your user event.

I have removed DC_CompleteEvents() from the code block in the upcoming build 255.

Roger

That is hard to believe.

Terry Wolfe had the same problem and I gave him the same fix.
It worked for him.