On a new server, a small number (8 out of dozens) of users get an ADS error 6420 on trying to start the ADS (DBF) driven program. This is what happens: 1 Error is returned on this line of code: ulRetVal:=DWORD(_cast,DBFAXSAdsIsServerLoaded(String2Psz(cDatapath),@usLoaded)) 2 If they restart the ...

Hello Luc, Very interesting as I get the correct results mixing the VO & X# program with SetAnsi(true). I don't set SetCollation but that shouldn't influence the actual strings, only the string comparisons. So we have now: 1 SetAnsi(true) in X# with ADS and DBFCDX and SetAnsi(false) for VO mixed use ...

Hi Dick, do you have ever tried to put a euro character in an ADS database field? At least with VO I was never able to do that.... Wolfgang Certainly, no problem. I can add it in a VO or a (Winforms) X# SLE, save it and it stores in the (ADS driven) DBF like any other >CHR(128) character. Here's ...

Thanks Chris, Wolfgang, to add: the 'explanation below' from the ADS help as Wolfgang posted is: "If the data is stored in the DBF as OEM data (to be shared with a Clipper application for example), it must also be collated using the Clipper collation sequence (which is ASCII for the English language ...

Robert, Chris, can you confirm this?

Dick

Frank works on an X# conversion and once he pastes an ANSI character in an SLE in a converted VO form, the character shows incorrect, unlike in VO. E.g.: straße changes into straáe . Once he runs SetAnsi(true) the problem is solved. However, we all use ADS which requires SetAnsi(false) to prevent b ...

Hello Karl, Indeed, nRowCount:=oRange:Rows:Count works without the setting, thanks. Often it's a bit of VO (or maybe Vulcan) created code with or without something more in this program. So instead of thinking what I am looking at (instance property etc) and what I should use I let the compiler ...

Hello Chris, Of course it makes sense what you write. The problem is that any project I restart working on after a few month or more, never works anymore which is frustrating. I must add to that that all the X# errors/ warnings were either quick to solve and those which were not were solved still ...

Hello Chris, Thanks for the further explanation; it makes sense. What I did is change REF to OUT everywhere I had a warning and these disappeared. I hope the program still works as it did. Furthermore no doubt there's a good reason for adding OUT which was not present in VO. As REF worked too (in VO ...

Hello Robert, Hmm, as I assigned something to all the variables in the meantime and simplified the code for posting I can't find it back to check if something in the code made the warning valid after all. If I encounter the warning again I will double check if something could cause it. As you tested ...