FiveTech Software tech support forums

... it myself, but surely Bruno may explain it better for us. Security is a must: your emails, your data, your privacy. Opening your router is quite risky unless you know exactly what you are doing and you perfectly know how to protect yourself. A hacker may get into your network and sniff your bank ...

... you don't have a reservation ID. However, you don't need to search for the recno() to find an open reservation. Using the recno() for an ID is risky since if a record gets deleted, then all the records after that recno() will get renumbered. That will be a mess. Thus you should always have ...

... then is as before then it add record I must save the new postion , dbzap my dbf and use FW_ArrayToDBF but it seems to me that this operation is risky then the archive must be opened in an exclusive way to use dbzap. I thought there was a less risky method like: change the position and save the ...

... You are already using OOP and I can't think of any better concept to reduce complexity and encapsulate program logic. 3) And updates are not so risky because not the whole application is addressed. OOP and encapsulation is one of the best ways to reduce risk. 4) I think you can also uniform ...

Hello Enrico, I think one can take out complexity from a program. You can start in a legacy app a new programming concept. And updates are not so risky because not the whole application is addressed. I think you can also uniform the look of your program. Better for sharing work in a company. Easier ...

... this, they can be forced to wait until your process is complete before performing the index file update. NOTE: Using this function, while somewhat risky, will improve your network performance by up to 100%, so weigh the options carefully. NOTE: This command is NOT supported under SIXNTX. Example: ...

Uwe

Your sample work perfect ...
But i have more than 100 dialogs with folders on them
It is risky to change logic to all of it , but i will probably try that with copy of the program

Thanks verry mush again for your reply

Best regards,

Uwe The sample : Thanks ... your sample work nice But the problem is with bigger applications with many dialogs, folders ... etc It is risky to implement this way karinha Use SENSITIVE SAY (SSAY.PRG) it solves. In which version is added SSAY class ... i dont have it SetDlgGradient() ???? ...

Avista, Using GO BOTTOM is risky since records may get deleted (unless the app doesn't allow it). If there were records created with that ID (invoices printed, etc.) then that record is deleted, it would get reused for a new customer. ...

... "Metro" succeeds, in a matter of x years, the Windows desktop will be at its end, and only the Metro way will continue. This try is very risky for Microsoft. They know it. If you take a Windows desktop app, it does _not_ work on Windows 8 "Modern" interface. More over, you have ...

... Not the Windows that we known and have used for so many years. And Microsoft is aware of this. In fact Steve Ballmer said that it was the most risky desition that Microsoft has taken in many years... I am not against Windows 8. I think it is a new OS and not what we call Windows.

When many Windows developers realize that they have to drop all their applications and know how, to push Windows 8 risky and quite absurd adventure, then you will understand why many companies are saying no to Windows 8 Metro... Microsoft may create a new OS is they want to, but ...

... Windows 8 Programming book you'll see that is a whole new world. Is like coding for the iphone. You have to start from zero again. Its a very risky situation...

... never declared as completed and there doesn't seem to be an active pool of programmers updating it after the initial work was done. So it's kinda risky using it unless one is a proficient C programmer who can update the code when necessary. I for one am interested in this class but have to shelve ...

... This would lead to lots of confusion. Not a good practice. Also, generating a new item number by going to the last record of an indexed file is risky. If the index becomes currupted you can end up generating duplicate IDs; I know because this has happened to me before. Duplicate IDs are a potential ...