FiveTech Software tech support forums

... some thoughts I'd like to share and discuss:

We all know it – constant notifications distract us from what's right in front of us.

Notifications tend to lead us into quick, superficial interactions instead of deeper conversations.
This can result in investing less in real, personal relationships ...

... and tries to defend them with responses that do not actually relate to your question.

AI is interesting, but it is sadly incomplete. Even so, people today tend to believe whatever they hear without actually checking it out closely, and therein lies my concern.

Oh, and I do have ChatGPT.

Dear Tim,

I just coded this little PRG and hbmk2 properly builds it so I tend to think that there is a preprocessor issue. Please compile it using -p to generate a PPO file and please check if such line gets modified, maybe a define is changing the code, many thanks:

This code generates an obvious ...

... believe debugging code was left in the 64 bit FWH 22.06.

When opening a dialog, I get a MsgInfo() saying TBAR, and then one saying TXBROWSE. These tend to repeat on any dialogs using the bar control and the browse control. It locks up the program.

The exact same code compiled with the 32 bit FWH is ...

... always my preference) I may hide the error using an HB_SYMBOL_UNUSED() call at the end of a func/proc and only use the pragma as a last resort.

I tend to keep all my fivewin code isolated from my pure harbour code, so it actually isn't a huge problem for me, but then again I did it years ago and ...

... always my preference) I may hide the error using an HB_SYMBOL_UNUSED() call at the end of a func/proc and only use the pragma as a last resort.

I tend to keep all my fivewin code isolated from my pure harbour code, so it actually isn't a huge problem for me, but then again I did it years ago and ...

James Bott wrote:Rick

Regardless of that issue, people do tend to judge a book by it's cover, and likewise, software by it's interface.

I totally agree with you on this point.

... Windows 11: Microsoft apologizes for compatibility confusion, hints at changes , by Ed Bott (no relation).

Regardless of that issue, people do tend to judge a book by it's cover, and likewise, software by it's interface. So if we can develop a Win 11 fluent design interface that runs on Win 10 ...

Rick said:

To All

Just my 2 cents ... I have found that corporate ( most users ) tend to import huge files into databases .. like ( lets say ) 1gb ++ .. .Dbf can get out of hand real fast if you allow that to happen .. that is why I prefer Sql Server using the fieldtype VarBinaryMax ( much more ...

Rick said:

To All

Just my 2 cents ... I have found that corporate ( most users ) tend to import huge files into databases .. like ( lets say ) 1gb ++ .. .Dbf can get out of hand real fast if you allow that to happen .. that is why I prefer Sql Server using the fieldtype VarBinaryMax ( much more ...

To All

Just my 2 cents ... I have found that corporate ( most users ) tend to import huge files into databases .. like ( lets say ) 1gb ++ .. .Dbf can get out of hand real fast if you allow that to happen .. that is why I prefer Sql Server using the fieldtype VarBinaryMax ( much more stable and ...

... there is an option.

Antonio: Will you be including any progress wheel with the FWH libraries ? It might not be as grand as these, but Windows does tend to use the wheels now rather than bars.

Thanks to all for your continuing contributions.



1. The price is what Antonio does for the new version ...

... Borland development tools. Thank you, however, for sharing there is an option.

Antonio: Will you be including any progress wheel with the FWH libraries ? It might not be as grand as these, but Windows does tend to use the wheels now rather than bars.

Thanks to all for your continuing contributions.

... all the records. That would seem to be easier.

Most of your issues are just due to you not yet understanding the use of database objects. Thus you tend to immediately blame the objects rather than looking for a coding error. It is not that the objects don't work. But the alternative (not using ...

... all the records. That would seem to be easier.

Most of your issues are just due to you not yet understanding the use of database objects. Thus you tend to immediately blame the objects rather than looking for a coding error. It is not that the objects don't work. But the alternative (not using ...