>> You can NOT use the same libraryes that used in FP 2.6 Dos with VFP, or >for that matter FP 2.6 Windows.. Sorry.. You will need to either get an >updated version, or try coding the features that you are using from the >library in VFP code.. >> >>Thanx! >Thanks for the information but I have another question. Does a bin file >have to be a library or can it be C code that is not compiled into an exe >or com file. >I don't know about the C compilers today but the old ones you could make a >bin file and load into a X-Base application. >Because it won't load that makes it a library from 2.6? It had to be compiled with ORG 0000 instead of standard ORG 0100, so it had no header; then it had to be made a .com file, and then it had to be converted with some utility like Exe2Bin, to make it a .bin file. Then it could be LOADed from anything ranging from FoxPlus 1.x until FPD2.6, but that's the end. It also had its limitations, like accepting only string parameters, crashing if string got any longer in the routine, etc etc. That's simply obsolete, and the first time got a V in its name, it was not supported anymore. I remember the last time we used it, it was for some serial communication with the POS display, some time in 1990. Just forget it - it is not supported anymore. If you have a way to call it from a .fll, then maybe it will work, but only by calling the function defined in the .fll, not in the .bin file itself (kind of a wrapper). Libraries (.plb in FP and FPD, .fll in FPW in VFP) had to be re-built for every new version of FoxPro for DOS, because the format had changed with every version, while I guess that .fll remained the same. .bin files are not treated as libraries - they are external routines which had to conform to some rules, so they could be called without Run command and could accept parameters and return values. This approach is not supported anymore.