hi all

i recently got an error message while in "define fields" saying that the file was damaged. this happened as i was saving a calculation. it gave me the choice to continue or exit. i had this happen to me a while back, but fm would just crash without giving me choice. when i called support they told me i maxed-out fields, i was at about 5900 fields. they said that how the fields were named would affect how many would be available. so i made some adjustments and everything's been fine. since then i've added fields and not had any problems. i had it to about 6500 fields when the problem at the top occurred.

i did perform a recover and it said there were no problems.

i also deleted some fields to get the count down to about 6200.

questions: has anyone ever heard of a field maximum?

if i choose to "continue" do i run a risk of crashes or problems?

i realize there's probably something i could've done differently in the programing stage, but i kind of learned as i created. that's another question when i can figure out how to word it.

let me know if you need further details to help you understand my problem/question.

thanks for the use of your brain.

FYI you are probably holding the record for most fields. Once you get up into the realm of a couple of hundred or so, it's time to start seriously thinking about restructuring your model. If I may ask: what the heck are you doing?

yeah i've been told that.

it's basically an invoicing/inventory file.

should i try to attach a copy?

I've NEVER seen an invoicing/inventory system with that many fields, and I don't want to!

Ditto. I thought my file with approx. 250 fields was a huge one. I can only imagine the number of duplicated calculations and nightmarish problems that you'd get with 6500.

please take a look

i threw this together so you wouldn't be looking at 6200 fields

i know there's something i should be doing differently, i just don't know what.

any ideas?

thanks very much

sample.zip

Without looking -- with relation you can have 2-10 files easily working together for stock, invoicing, invoice lines and customers...

Redesign is long overdue.

I think it will be unanimous consensus among FM developers in this topic.

6500 fields!!!! Sounds like maintaining that would be just total hell.

Thanks for not uploading your 6500-field sample. I looked at the file you posted, and I see that you're tracking pieces of clothing with bar codes.

You included a note that says "many items = many fields."

No, no, no. Many items = many RECORDS.