How do you reference or export summary fields?

[cseow]

Not sure if this is the right place to post but here goes

[Kurt Knippel]

quote:

---

Originally posted by cseow:

Not sure if this is the right place to post but here goes

[rogermax]

Is there a way to accomplish the export to file then import to another db all in one scripted sequence so the user never knew they did that? I can see some powerful technics that I have been pondering for some time.

This would be used primarily in a windows environment so applescripting is out for my needs.

[proton]

quote:

---

Originally posted by Roger Maxwell:

Is there a way to accomplish the export to file then import to another db all in one scripted sequence so the user never knew they did that? I can see some powerful technics that I have been pondering for some time.

This would be used primarily in a windows environment so applescripting is out for my needs.

---

Roger Maxwell,

Simple...First do the export manually, set all the options and so on. Next, go to the other filemaker database and do the import manually. Next go back to the 1st database and create your script, include the export script step. It will allow you to specify a file and location. Select the same file you first exported to, and tell it to export without dialog. Next click on OK, it will ask you if to keep export order, say yes (Keep) and then click done (let's say this is script A).

Go to the 2nd database (where you import the summary data). Create a script (script . Select the import script step, specify the file you imported the data from and tell it to perform without dialog. Click on OK, it will ask you if to keep import order, say yes (Keep), click done.

Finally, go back to 1st database and open scriptmaker and edit script A, as a last step add the perform script step, select external script and specify the 2nd database and select script B.

You're done. Hope you understand all this jibberish.

[DykstrL]

Instead of exporting and re-importing the data, why not use Globals to capture the information from the summary fields?

SetField(GlobalField,SummaryField), etc...

The information could then be moved to other records/fields or to related files. This could all be done via scirpts.

[Kurt Knippel]

quote:

---

Originally posted by dykstrl:

Instead of exporting and re-importing the data, why not use Globals to capture the information from the summary fields?

SetField(GlobalField,SummaryField), etc...

The information could then be moved to other records/fields or to related files. This could all be done via scirpts.

---

This is fine when you know EXACTLY how many summarizations that there will be. If summarizing addresses by street, how many globals do you need to store the totals for all the different streets?

I have used your suggestion in many occasions, usually for totals and subtotals, because I know all the variables but the actual answer.

However in a normal situation where you want all the summarized values, it is generally unknown many there will be. Thus you need to export to fix those values into what amounts to multiple fields (one for each field summarized) and multiple records (one for each summary).

[cseow]

Hi All:

Thanks for all the suggestions - particularly Kurt. It's helped me achieve a work-around to a problem I've been facing.

Just wondering though, can the ODBC features of FileMaker be applied in this type of situation?

[Kurt Knippel]

quote:

---

Originally posted by cseow:

Hi All:

Thanks for all the suggestions - particularly Kurt. It's helped me achieve a work-around to a problem I've been facing.

Just wondering though, can the ODBC features of FileMaker be applied in this type of situation?

---

Possibly, because you can structure a SQL query that performs the summaries.

Is the SQL/ODBC way a better answer? I do not know.