How to precisely define numeric datatypes in foxpro table using clarion dictionary

questions
21

I just saw on Clarion-help about using the external name on the attributes tab

If your application reads and writes to existing files, a pictured STRING will suffice. However, if your application creates a dBase III file, you may require additional information for these dBase III types:

* To create a Numeric field in the Data Dictionary, choose the REAL data type. In the External Name field on the Attributes tab, specify ‘NumericFieldName=N(Precision,DecimalPlaces)’ where NumericFieldName is the name of the field, Precision is the precision of the field and DecimalPlaces is the number of decimal places. With a REAL data type, you cannot access the Character or Places fields in the Field definition, you must specify those attributes with an expression in the External Name Field on the Attributes tab.

For example, if you want to create a field called Number with nine significant digits and two decimal places, enter 'Number=N(9,2) in the External Name field on the Attributes tab of the Field properties in the Data Dictionary.

22

I imported both files into a Clarion dct, using Foxpro as the driver. This auto defines the field sizes.

The Actual file has two values that I couldn’t get to display when viewing the file from the dct file browser.

I Wizarded an app from the two files. The same 2 values wouldn’t display in a browse, but they did display in the update form and I could edit them. When I tried to save the updated values I got an “Unable to frame transaction” error but the file updated anyway and the values now displayed in the browse.

I have no idea if the edited file is now usable by your Foxpro app?

23

Unfortunately, I have no access with their foxpro app, They just need us to send a file that is readable by their foxpro app. The only key to proceed is to give me their actual file that is readable by their app.

24

Wow, this does the trick. Thank you so much.

OLDGT               REAL,NAME('OLDGT=N(14,2)')

I would never thought about external names, it’s like imposing a rule that this datatype should be built like this.

May I know where did you find that in the clarion documentation? Thanks in advanced.

25

Hi Chris.

Glad it worked for you although you may need 20,5 to match the supplied file.

I am away hiking with only my phone so couldn’t check Clarion help on my PC but fortunately @seanh has kindly set up Clarion.help and I think the information was under dBaseIII:specifications so as Sean’s web site is basically taken from the Clarion help files you should find it there in the Clarion help.

26

I think it’s okay for now as I have been able to replicate the exact structure of the actual file they have sent using the solution you have provided. This really helps a lot.

Thanks again. :sweat_smile: