by Richard Chidiak » Sat May 11, 2013 10:48 am
Antonio
It is a good idea moving to the ide.
One imortant thing to mention, all problems i had were more related to Harbour than Msvc. I had exactly the same problems with Harbour/Bcc than Harbour/Msvc. probably Xharbour is more permissive in different ways, it is a fact , my application was rock solid. I faced strange problems going to Harbour.
1. Ini file nor found by Harbour, no problem with Xharbour, the file was present .... Solution delete the file and create it again !
2. Ole complete different syntax.
3. Mdi windows exit ... completely different from Harbour to Xharbour
4. Calling a dialog twice in a mdi window crashed the application... had to modify the class and the way to end the window to have it working properly.
5. Still have a problem with a dialog (settings) in a mdi window, closing the dialog, window = OK, come back again enter dialog = crash at validate.... This is the ennoying part related to Harbour, i am not sure the ide's debugger will help us with it.
6. Resources : static texts that are > 256 chars are truncated to 256 , Bcc does not have this limitation
As per Tim's problems with Database crashing in the component , better check if odbf is Ok with Harbour or if some extra syntax or parameter is needed. The problem here is neither codejock or Msvc but Harbour. I use dbfcdx and fully tested this part with customers, OK. Maybe some friends using Harbour and Odbf can comment on this one, it can help Tim.
As a conclusion moving from xharbour to harbour is probably the way to go but we need to asure 100% compatibility. Lots of tests are needed. Not as simple as we could imagine.
My 2 cents.
Antonio how to build Harbour from the Ide ?
Richard