Raymond P McIntosh 25.Apr.12 03:01 PM a Web browser Approach9.7Windows 7
I need my memory refreshed. I have a data base with a fairly modest number of records, but each record has a huge number of fields--so many, in fact, that they far exceed the 255 field limit for Approach dBaseIV files. I've solved this by creating several different data bases and joining them all to the primary one, thus giving myself 255 fields times the number of data bases. But what I'm fuzzy about is the impact of calculated fields. As I recall, calculated fields (and some others, variable, I think) exist only in the Approach file, not in the .dbf file. And I think I recall reading somewhere that calculated fields do not count against the 255 field per database limit, because that limit is a dbase limit, not an Approach limit. What I'm also not clear about is whether a calculated field can be created ONLY in the primary data base, when multiple databases are joined, or if they can be in ANY of the joined databases. When I look at the field lists, the calculated fields appear in the field list for EACH of the joined databases, so it appear that a calculated field created in the primary data base Approach file also becomes a calculated field in all of the joined files. But, as best as I can recall, I've never actually tried to create a calculated field in any data base except the primary one. So, my questions are:
1. Am I correct in my understanding about calculated fields existing only in the Approach file, and that they don't count against the limit of 255 fields per file?
2. If so, is there any limit to the maximum number of calculated fields in an Approach file?
3. Finally, if there IS a limit, can it be overcome in thee same manner as I overcame the limit of other fields--that is, by creating the calculated fields that exceed the limit in another joined database.
Return to top
Approach Limits (Raymond P McInt... 25.Apr.12)
. . 
Print this page
