FiveTech Support Forums

I am curious what FWH version people are using for actual production work ( released product ).

The latest released version is 17.09, however, I know several of us had to re-vert to 17.06 or .07 database.prg to resolve problems with the new database revisions. I'm wondering if anyone is able to use just 17.09 in their production work with .dbf files, and without problems. If so, did you make any modifications to give it stability ?

If you were not able to get it to work properly, what are you now using for your work on released product.

Thanks for the input. I guess I'm wondering if I'm the only one having issues ( maybe I should retire ) or if the problems are more universal.

Tim

Currently , I'm using FWH 17.07.

I see 17.11 posted today but there is very little addressed in it, and nothing related to the database.prg issues raised in September by many people here. Thus I might suspect I missed some notes about how to resolve those problems.

TimStone wrote:I am curious what FWH version people are using for actual production work ( released product ).

The latest released version is 17.09, however, I know several of us had to re-vert to 17.06 or .07 database.prg to resolve problems with the new database revisions. I'm wondering if anyone is able to use just 17.09 in their production work with .dbf files, and without problems. If so, did you make any modifications to give it stability ?

If you were not able to get it to work properly, what are you now using for your work on released product.

Thanks for the input. I guess I'm wondering if I'm the only one having issues ( maybe I should retire ) or if the problems are more universal.

Tim

I am using FWH 17.09 for my production work with out any problem.
I feel that TDatabase Class of 17.09 is the safest one.

Because It has brought out some of the obscure bugs in my earlier
programs.

Tim

I am using Fwh 1707 and I gave up on .Dbf years ago, all my HIPAA ( state clients ) had security issues of having .Dbf(s) on their network shares where anyone could open a .dbf with Excel or could maliciously delete all the datafiles in one fell swoop.

I went strictly with Ado converting all my code to Sql and my database(s) of choice are either a ( secure ) MsSql Server or ( the stand alone un-secure option for clients that can not afford an Enterprise RDMS ) Ms Access ..

All I use .dbf for is when I need to create reports and then I only use temp .dbf in Exclusive mode .. said bye to OptLocks many years ago and never looked back.

Rick Lipkin