FiveTech Software tech support forums

Hello Harvey, It seems, oSAY1:lTransparent := .T. is not needed for Transparent-painting. Just define the DIALOG transparent, it will make it easy for You. DEFINE DIALOG oDlg5 RESOURCE "TXTTEST2" TITLE "Text-Test" ; FONT oProgFont TRANSPARENT REDEFINE SAY oSAY1 VAR cText1 ID 110 ...

I want to set all dialogs (resources) to have transparent says. There are many dialogs with 100's of says. I need to add in each function oSay:ltransparent := .t. and many of the says are different and all local. Its a big job. Anybody have any suggestions?

All help appreciated as usual.

... arrow pointing into a folder. Deleting a record could be a - sign, or a trash can, or a circle with a line through it. Printing is pretty universally a printer, but what about history ? ( I use a folder now, but a file cabinet could work but I like the simple designs best ). The icons ...

Since I would only use the newer balloon style universally, its OK with me, but adding a line of code for a button bar isn't that hard. Of course, tooltips with gets would add a lot if each one was set individually.

... way of #translating the "locate" or "seek" command to something like : cSQL := "reg_no like '"+cFIND+"%'" oRs:Find( cSQL ) .. This seems to work universally with all SQL engines and ADO .. If you decide to go down this path .. RDD EOF() and not found() will need to be #translated to oRs:eof Set ...