![]() ![]() ![]() Have you tried Lotus Approach? Excellent database program, the OS/2 version had bugs in the join creation code that would sometimes make it crash while creating joins, but once they were created the resulting database was stable. Note that there is an Asian company of the same name that has no relation to this one and has a funny homepage with their logo photoshopped on impressive looking buildingsĪctually a Kiwi rather than an Aussie as I had remembered it, the gent that runs the company is called Brendon Edward Deere and he posted to OS/2 groups from time to time in the 90's.Īnd as for your interest in R:Base, the 16 bit version worked extremely well in its time, cannot remember using the 32 bit one. The company is now called "ITL Aviation Limited" and is still around although by now out of the oil and software business. In reply to your (now deleted!?) post, the last contact info for the gent behind Base32 was: You may also take a look at Harbour, it is similar to X2C with more modern syntax, however I think that the OS/2 port only works properly with IBM VAC++ and older versions of GNU C as back ends, neither of which is as user friendly as Watcom in eCS. Since the output code is a well defined C subset it might even be possible to merge it with one of the PD Mini C compilers into a program that compiles executables on its own. Just a few modernisations to make it slightly less work to compile in one go and so on, might be all that is needed, it might even be as little as a few REXX scripts. X2C is a dBase/Clipper/xBase compatible compiler that pumps out C code that is ready for compiling with a C compiler and would probably work with Watcom as is, as it outputs very clean C code but the current version has only been tested with Borland C++. The gent behind Base32 disappeared around 2003, but I might have old contact info here somewhere, I was just thinking aloud since Martin was wandering if he should contact OnCMD, that tracking down the guy behind Base32 would be a better idea. Since dBase and Clipper had no real problems with character sets in the database file this entirely artificial limitation sort of blew my mind when I bought a license in the late 90's, especially considering how good the rest of the code was, and how $#%!#$! expensive my triple target developers license was. The problem with ASCII only, means no extended characters whatsoever in the database itself or code, no graphic symbols when porting from old DOS code, no NLS characters in the data (no ð or þ for instance) not even accents, so no French é or Swedish ö or ligatures like æ. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |