There is no such option. After importing the data, you'd have to go to Manage | Database and change the field type to number. Either that or you define the table in advance and specify the data types then, before importing into what is now an existing table.
I was afraid of that... only about 1000 financial data fields to manually set!
That seems like an extremely excessive number of fields. Any time your number of fields exceeds 100, it's time to review your data model to see if there are better alternatives.
We track quarterly financial reports from financial institutions. Our table structure is one table containing institution names and one table containing all quarterly financial report data. The relationship is defined by a unique institution ID in both tables. We've run it where the financial data was split across multiple tables but we end up with too many relationships (we have multiple relationships used for ratio calculation purposes).
Apart from splitting the data as I just described, I'm not sure what other models you might be thinking of. Love to hear.
That's not something I can suggest from such a limited understanding of your current data model and what you need to do with the data once it is imported.
Too many relationships? This is a relational database after all, not a spread sheet program. What problem did that cause for you?
I say "too many" relationships because in setting up ratio calculations for current and historical periods we need multiple instances of the same sets of tables. When we had the data spread across multiple tables it made adding new calculations cumbersome.
Kind of hard to explain without dropping a screenshot into the forum, which is not something I really want to do - but I will certainly acknowledge that the structure of the database could probably be better.
That doesn't sound like something that should require adding more and more relationships with more table occurrence groups (instances of the same set of tables).
Even if it does, ExecuteSQL would probably handle that issue.