FiveTech Software tech support forums

... several years ago that disabled many client server systems ( including ADS ). They never provided any way to work around the problems. It also messed with Oracle services. So I do not see them making any changes in the future to accomodate older OS operations.

... was all written in clipper, the code below was perfectly formatted in a DOS box. However, when I use them in a DIALOG, the spacing is "all messed up" First, the GET boxes are on different rows than the SAY statements. They are higher Also, the columns don't line up. Of course this ...

The Print command is really messed up in recent versions of FWH. In fact, in the command print oprn cprinter, as you described, cprinter is ignored completely. The only way to get that to work is to first set the windows default printer ...

Tim,

I replied to your email shortly after you sent it. I upgraded from Win8.1 to 10 yesterday so it is possible something is messed up. I will check my online email account to see if the sent mail is there (I can't see any sent mail in the Win 10 mail app).

james

Antonio I am still puzzled, all those values are messed 6.2 is windows 8 6.3 is windows 8.1 so if you force 6.3 in iswin10() , windows 8.1 will return windows 10 i think the most reliable way is to test the product name below is a copy of my registry ...

Thanks Rick, Well after considerable headaches, I found the problem. There was a Microsoft Security Essentials update that went wrong and basically messed up all my security settings. Once I removed it and re-installed, everything came back to normal. What a pain the B..... Thanks for your input ...

Ok, i sorted out the first issue.

I still have the problem of the date being messed up in the Listbox.

Any ideas?

... the system that reads the .txt file) would be set to the same format. I also notice that when set to this format, my dates in my listbox are all messed up. Ex: 08-Sep-69 (as seen in my datepicker field) shows as 08-009-969 (as seen in the listbox) In Windows date settings, this format is listed ...

... The 1st time out the TxBrowse is displayed everything is OK. The problem comes when I skip through my records, then the array gets all messed up. When I get new record to fill the TXBrowse array with: DBSKIP(-1)*Same code as before to fill the array….  oBrwD:aArrayData := aResult ...

... / oRepo:oDevice:nLogPixelY, RightMargin( oRepo ) / oRepo:oDevice:nLogPixelX , 1 ) } works with cutepdf writer but not with Epson. I probably messed something in the box params. I reduced font size to -1 Now the results of testing : In CutePDF and Foxit Reader PDf Printer master data fits ...

... / oRepo:oDevice:nLogPixelY, RightMargin( oRepo ) / oRepo:oDevice:nLogPixelX , 1 ) } works with cutepdf writer but not with Epson. I probably messed something in the box params.

I figured it out

It was a poorly used ".and." that messed everything up.

I had done something like this:

Code: Select all  Expand view

IF nRow > 275 .and. nGraphSize = 0

Where it should have been:

Code: Select all  Expand view

IF nGRaphSize = 0
   IF nRow > 275
 

Thanks to all for your help.

... in my previous code example. Changing these two lines to maximize the MDI child window before setting focus, will fix a screen that has been messed up by the user selecting to cascade, split vertically, or horizontally the open windows. Regards, James oPanel1:AddLink( "Providers", ...

Nuevo build disponible: * Fix: Coordinates were also messed in Class TDialog. Now they are fine. * Fix: Coordinates were messed in Class TWindow. Now the specified coordinates are right: DEFINE WINDOW oWnd FROM nTop, nLeft TO nBottom, nRight Please ...

* New build available: * Fix: Coordinates were also messed in Class TDialog. Now they are fine. * Fix: Coordinates were messed in Class TWindow. Now the specified coordinates are right: DEFINE WINDOW oWnd FROM nTop, nLeft TO nBottom, nRight Please ...