Re: need help with foxbase

[Lawrence Lustig]

Bernie:   A year or so ago, I converted a client's Foxpro 2.5 for DOS application to RBWin (latest and greatest).  The amount of code in the application was reduced by about 90%, which gives you an idea of the efficiency of R:Base compared to Foxpro programming. I know that rbase can read those files.  I also know that each table is a separate .dbf file. R:Base can read dBase files.  Foxpro files are much like dBase files BUT WITH A DIFFERENT MEMO FILE FORMAT.  Therefore, R:Base cannot read the Foxpro memo files.   In addition, you see a lot of strange formatting used in old xBase files, especially different ways in which the programmer chose to represent dates.  In the project I did, one table used three different formats to store dates.  R:Base has tools and commands to convert all of these, just make sure to plan for the extra time.   Also, Foxpro does not have domaining, implicit or explicit, and so you may very well find that columns with the same name have different data definitions. But how do you get to see the relationships between the tables and where are the forms and reports located and how do I get into the program. You can't see the relationships between tables because there are none in the tables -- only what is enforced through code.  This is often done by USEing tables in two workspaces and using the SET RELATION ON command, but there are other ways.  Probably the best way of starting to look for them would be to look through the forms and reports.   Forms and reports are stored in separate files, one item per file.  Because each goes through a couple of formats (similar to CODELOCKing in R:Base) you need to make sure you have access to the source for each one.  The editors and compilers for each format are in the Foxpro program itself.   To start the program, look for the FOX or FOXPRO EXE file.  I don't need a course in fox, just enuff to look at the program.  Naturally, my goal is to get him to move into rbase, so I would appreciate any help I can get. Go for it -- believe me the resulting application will be enormously easier to maintain.  If you have any more questions don't hesitate to ask. -- Larry