Antonio,
Thank you. Now it is.
So please, what was the mistery?.
Thanks.
There are no misteries, its just a matter of learning and investing time using Microsoft C 
The more I use Microsoft Visual C the more I like it
Antonio,
Do you recommend me a particular book about MSVC?.
Also, I am worried as you said that in FWH64 DLL32 calls won´t work properlly. Please, could you be more specific?.
Also, when you have time, as it is not urgent, you could provide us some advice in editing .rc files with Msvc. It has a built in editor quite familiar to the great WorkShop, but when I save the .rc MSVC adds other things that broke it.
Btw, what .rc editor do you use?.
Thank you very much Master.
Lucas,
I just use the tool and google. No need for books or lets say google is the best book
I think I already have the solution for the DLL FUNCTION and LONGLONGs. I have to do some more tests.
I use PellesC but I will spend some time with the Visual Studio one to get used to it too.
Antonio,
Have you consider the seminar for C and FWH?.
Thanks.
Antonio,
So, when do you think FWH64 would be stable for production?.
Many thanks.
Lucas,
I am available to provide a C and FWH seminar, but honestly I don't think that it is needed as FWH sources are a great way to learn it, and to learn just the code that we are going to use (no need to know everything about C, unless you feel passionated about it).
Elvira,
In my opinion FWH 64 was and is ready for production, in fact there are FWH users working with it. We do many tests with it and works great (from FiveDBU to rbdesign.prg, etc. we simply missed to use RichEdits with it).
It is just that Windows 8 revealed some hidden problems that had to be fixed and have been fixed. RichEdit was failing and now it is fine. Same applies for Class TWebCam that worked always fine but we forgot to include it in the libs. I have to review an issue with LONGLONGs, not sure yet if it is a problem, I just want to check it to asure that it is fine.
Antonio,
Thank you. But I understood from your comments that the product was not readu 100% and some class es could fail.
The App you are coding with Access, have you buit it with FWH64?.
We think that providing a 64.exe could be a new market nish to explore?.
Best wishes,
Elvira,
We started FWH 64 development around 2005 and we have been pushing it and trying to promote it for all these years
A lot of tests have been done with FWH 64 with excelent results, but as FWH is a huge product, not every single control was tested (Not all FWH features are usually used from a FWH app), and on those where an error has been detected we quickly provided a fix for it.
So I would say that FWH 64 is very mature and stable, but of course the more users that work with it, the fewer bugs that it will have. Lets remember that FWH 64 was born as a port from FWH 32 and that many source code sections have been
adapted for 64 bits. The best way to test it for yourself is to build your app with FWH 64 and get your own conclusions
Elvira,
We have built and tested FiveDBU.prg and many others apps with FWH 64 and it works really fine.
We are building a large app using ADO and Access and we have not tested it with FWH 64 yet, we will do it asap, thanks for the reminder
Antonio
I would be most curious for you to share your progress, lessons learned using 64 bit ADO and MS Access. I have written several recent applications using .mdb .. I dabbled briefly with ACE and .AccDb and found it compatible with .mdb with the only exception being the connection string and having to distribute the ACE ole provider client.
Thanks
Rick Lipkin
+1
