FiveTech Software tech support forums

Mr. Rao and friends I apologize, after several nightmare nights, I have finally solved the problem, the problem was in the last line of this code. [code] oRsWrk := FW_OpenRecordSet(oApp:oCon,"SELECT " +; "*," +; "RUB_DES," ...

... anyone might like to donate for a good cause .. I can embelish the field names .. it is the layout for multiple envelope sizes that present a nightmare for me .. Thanks to All Rick Lipkin

... it is too complex to build a simple example, it seems that the solution would be to migrate to Harbour and MSVC, But for legacy systems it's a nightmare. it seems that the solution would be to migrate to Harbour and MSVC, im already try, but i work in portable way, and dont have an msvc portable. ...

Michel,

I would think that would become a nightmare. What is the reason that you want to do this?

James

Only mod_harbour CGI is truly functional.

All other versions will crash Apache and the server itself.

You should trust what I am saying, as it is based on me and my team tests in a large company for three years.
And it became a nightmare until we decided to go the CGI way.

... in the stored procedures needs to be updated on all the databases. The chances of making mistakes are high and as days go by maintenance becomes a nightmare. If you go for one single database model then just keep a public variable in your PRG to identify the CompanyID while starting your application, ...

... in the stored procedures needs to be updated on all the databases. The chances of making mistakes are high and as days go by maintenance becomes a nightmare. If you go for one single database model then just keep a public variable in your PRG to identify the CompanyID while starting your application, ...

... have to add it (and troubleshoot it) everywhere you add, delete, or update records. And wherever you open tables. Using and tracking aliases is a nightmare which only gets worse as your program grows. With objects, you have to get used to some change, but in the long run it will take way less ...

... have to add it (and troubleshoot it) everywhere you add, delete, or update records. And wherever you open tables. Using and tracking aliases is a nightmare which only gets worse as your program grows. With objects, you have to get used to some change, but in the long run it will take way less ...

... a customer to be deleted then you would also have to delete all related records such as orders, invoices, etc. You can see that this could be a nightmare. What about unpaid bills, unprocessed orders, etc. You would have to do all kinds of checks before even allowing a delete. Much better would ...

... an archive and at the same time reopen it from another part I'm afraid that I get the message "alias do not exist" this is and it was my nightmare 15 years ago for this reason I had abandoned and embraced the exclusive way

... network discovery options. It may well be that what you are experiencing is a side effect from that update. For those of us who use ADS it was a nightmare. I have also seen strange issues with Windows Explorer in the latest version of Win 10. Good Luck Tim

... think that FWH has now reached its full maturity, fruit of many years of research and development. Now it would be perhaps to start again another nightmare that cost many years to stabilize. I love FWH. I want FWH. I need FWH… (If my wife hears me she will hit me with a bat 2 times ...) But I ...

Hi.
I've tried your suggestion but the error messages inside a procedure are still there.
Maybe the messages that are disabled with that check are others.
It's a nightmare.
Thanks a lot
massimo

Marc, First let me say that this is a nightmare senario. The best solution is to prevent the problem from ocurring in the first place. When you say "online" do you mean the database is accessable via the internet? If so, they why isn't ...