On 17/04/12 10:46, Norman Dunbar wrote:
The compilation worked, but listed calls to strfnd as having the wrong
number of arguments. I had three, as per online references, but it seems
the definition in string_h only has two :
strfnd(const char *, const char *)
So, I fixed my code to remove the third (boolean) parameter, and
compiled again.
Which allowed it to compile ok, but running it (see below!) shows that
it can no longer use the LOCATE/CONTINUE commands to find data in the
sorted field - always returns no records found. The normal FIND command
is ok.
LOCATE uses strfnd() so I suspect it's been affected by the change to
two parameters from three..
Checking the map file, I see _OSERR is undefined.
I then changed all my own code to use errno_h and errno instead of
_oserr, but that gave the same result, _OSERR is undefined.
It may be because the DBAS library call fsd_open also sets _oserr on the
event of any errors, so this last one might need some jiggery pokery to
get around, but I'll appreciate some assistance on the remainder please.
I'm still getting the undefined _OSERR error in the map file, but I
noticed that an executable was still being created. I took a chance and
it runs ok! Hence my ability to determine that LOCATE/CONTINUE (above)
were not working.
Interesting!
Cheers,
Norm.
--
Norman Dunbar
Dunbar IT Consultants Ltd
Registered address:
Thorpe House
61 Richardshaw Lane
Pudsey
West Yorkshire
United Kingdom
LS28 7EL
Company Number: 05132767
_______________________________________________
QL-Users Mailing List
http://www.q-v-d.demon.co.uk/smsqe.htm
