Structure of data in Filemaker
Hi!
Since Im new to Filemaker I would like to have an explanation how its data is stored and suggestion how to export it most efficiently. I hope I can make myself understood even though I use "Access vocabulary" :-)
I connect to a FM DB with a lot of information placed in different tables, and some fields use lookup and calculation functions.
When I try to fetch data from Filemaker, it seems to hang some times and I guess its because of the lookup and calculation functions. I try again and again and after some tries it works.
I only need raw data from some of the tables, not those calculations. Can I make FM to skip calculations when I get the data? I have tried to select only my preferred fields, but it doesnt seem to work.
Thankful for any clues / suggestions!
Btw, the FM database is not developed by me as you probably understood already.
I have experimented with both ODBC (Asp) and Datavations FM Connect.
Since Im new to Filemaker I would like to have an explanation how its data is stored and suggestion how to export it most efficiently. I hope I can make myself understood even though I use "Access vocabulary" :-)
I connect to a FM DB with a lot of information placed in different tables, and some fields use lookup and calculation functions.
When I try to fetch data from Filemaker, it seems to hang some times and I guess its because of the lookup and calculation functions. I try again and again and after some tries it works.
I only need raw data from some of the tables, not those calculations. Can I make FM to skip calculations when I get the data? I have tried to select only my preferred fields, but it doesnt seem to work.
Thankful for any clues / suggestions!
Btw, the FM database is not developed by me as you probably understood already.
I have experimented with both ODBC (Asp) and Datavations FM Connect.
ASKER
Ok, thanks!
Not 100 000 lines, no, but 10 000. But the datastructure seems to be pretty complex. Perhaps I force FM to give me the calculated fields.
Hmm... Slow ODBC, yes, but when I use Datavations FM Connect, it uses Web Share, not ODBC, but it seems to be as slow as ODBC. Why?
How about using FM to write into Access? What do I need to make that work (automatically every evening)? FM Developer? Do you have some good link with a sample?
Regards
Jonas
Not 100 000 lines, no, but 10 000. But the datastructure seems to be pretty complex. Perhaps I force FM to give me the calculated fields.
Hmm... Slow ODBC, yes, but when I use Datavations FM Connect, it uses Web Share, not ODBC, but it seems to be as slow as ODBC. Why?
How about using FM to write into Access? What do I need to make that work (automatically every evening)? FM Developer? Do you have some good link with a sample?
Regards
Jonas
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
non stored calculated fields are not calculated unless you display/print/request for them, so this is not the reason for the base to be slow normally. How big is the base(s)? over 100000 lines? If you have any doubt about this, duplicate the FM base to have a backup, and delete caculated fields to make a test.
In any case, it would be faster if you would use FM to write into the access base using ODBC.