Well I have not used Clipper in the better part of 2 decades and I found some old source code of an application I wrote and thought it would be a it of fun to resurrect it in the the windows world - apparently there is still a user or two out so it might help them. I choose the latest Marinas-IDE, if there is a better tool for taking this to a windows environment with @SAY GET equivalents let me know.
.. I choose the latest Marinas-IDE ..
looks not bad - this seem to be 'only' a combination of Harbour plus something own GUI above all plus the separated Harbour QT-project
-- including all these memory leaks etc. from the last piece ;-)
Workflow get running in console mode, then modal windows and then maybe MDI.
Now the problems.I am very impressed with Harbour my only real problem getting a compile was clipper tools functions & funcky functions that are not supported. For the time at least these are stubbed out.
Harbour has the additional contrib library: hbct
which contains nearly all <C>lipper <T>ools functions - works from finest !
But i fear that you will have no luck with the Funcky lib. There are others available, but i don't know of freaky funcky ;)
So you will need to translate/ transform these function calls ...
Now ALLTRIM is causing me grief - and I use it a lot -- when passed a variable holding a NIL it falls over. This is different to clipper because the app used to compile and run.
:-) -- I checked against original ! Clipper V5.2e (IMHO best version ever):
ALLTRIM( var_contains_nil_or_not_string )
leads to error:
"wrong argument: ALLTRIM"
which is exact what should expected when reading the original documentation:
http://x-hacker.org/ng/53guide/ngc2e2.html
Next problem..DBFCDX indexes are truncated to 10 char....is there any core RDD that allows longer than 10 char index names?
[ BTW. function name is either TRANSFORM or TRAN, when shorted to 4! letters - it is a wonder that Harbour even supports that ]
About 240 is max length of an index key - 10 is the standard length of an index key, if the length is improper defined ! - exact like Clipper did.
For this length estimation when index is created, a BLANK value of the given field is evaluated.
Maybe show us your [missing] improper RECNUMPIC
Regards
Rolf
What GUI has the biggest following and most frequent updates?
... hence my current search for an RDD that has similar functionality so I do not have to truncate my index names to 10 char - which I find hard to read and maintain. I appreciate Harbours drive for Clipper compatibility - which is really very close - but some things like this could be modernised without impacting Clipper compatibility.
I ultra strong believe of an error on your side - when indexing or seeking. Something i can't see from here, check also field types etc., as f.e:
TRANSFORM( "elch", "999999" ) leads to "".
Try to view (don't edit) the index file with a hex editor, there you should be able to see your index keys.
Start debugging to verify the index expression at runtime, check result with [x = index order]:
&( INDEXKEY(x) )
...
Regards
Rolf