Re: automatic field creation
- From: Lynn Allen <lynn@xxxxxxxxxxxxxxxxx>
- Date: Fri, 24 Aug 2007 21:04:24 -0700
X-Trace
User-Agent: Unison/1.7.9
NNTP-Posting-Host: 66-214-13-172.dhcp.lnbh.ca.charter.com
X-Trace: news.bnb-lp.com 1188014664 66-214-13-172.dhcp.lnbh.ca.charter.com (25 Aug 2007 00:04:24 -0400)
Organization: Send abuse or DMCA complaints to abuse@xxxxxxxxxx
Lines: 52
X-Authenticated-User: vca037
X-DMCA-Complaints: Send abuse or DMCA complaints to abuse@xxxxxxxxxx
X-DMCA-Complaints: The subject line should contain only the 4 letters DMCA
Path: mail.derkeiler.com!drt1!artnm!t1!feeder.news-service.com!feeder2.cambrium.nl!feeder1.cambrium.nl!feed.tweaknews.nl!nx01.iad01.newshosting.com!newshosting.com!216.196.98.140.MISMATCH!border1.nntp.dca.giganews.com!nntp.giganews.com!news.bnb-lp.com!not-for-mail
Xref: mail.derkeiler.com comp.databases.filemaker:114322
On 2007-08-24 12:36:12 -0700, Diego B <messadua@xxxxxxxx> said:
Actually there no that many calculated fields (no more than 40,
globally, maybe less,
do you think this could be the problem ?
I noticed that, when I use the tabs in the layouts FM slows down
noticeably.
I would avoid using Tabs, but there are so many fields in the Echo
Table that I am forced to
do that. Is this problem recognized somewhere or I am the first to
report it ?
I suspect it's not the tabs it's the fields displayed on the tabs. Yes, 40 calculated fields could slow down a solution depending on how many related fields they refer to or what the calculation is. No one else has reported tabs as a performance drag.
I like this idea, more than auto-enter option.
The script should be something like
set field:: Doppler_GlobalAverage
Insert calculated result:: Average (Basal_Lateral; Bas_InfSeptum;
Bas_InfLat etc...)
I would put the calculation directly in the Specify dialog of the Set Field. Insert calculated result is redundant, and that script step requires that the field be on the layout. Set Field does not.
And if you're using Average on screen, that's DEFINITELY the cause of your slowdown. Every time you move from record to record, or from Tab to Tab, every Average field that displays will have to re-evaluate in order to display.
An average of values on the present record can easily be set by script and be valid.
If your Average covers all records in the db, then every time you enter a new record the average will change for all records, and this is not a good candidate for scripted setting, because the values in all other records will become invalid.
In that case, you'd need to restructure your db to only display average or other summary fields on specific layouts or on reports, rather than on live layouts where you enter data.
--Lynn Allen
--
www.semiotics.com
562.938.7890
Member Filemaker Business Alliance
Long Beach, CA
.
- Follow-Ups:
- Re: automatic field creation
- From: Diego B
- Re: automatic field creation
- References:
- automatic field creation
- From: Diego B
- Re: automatic field creation
- From: Bill
- Re: automatic field creation
- From: Lynn Allen
- Re: automatic field creation
- From: Diego B
- automatic field creation
- Prev by Date: Re: Unsort a valuelist
- Next by Date: Re: Vista x64 and Filemaker Pro ODBC
- Previous by thread: Re: automatic field creation
- Next by thread: Re: automatic field creation
- Index(es):
Relevant Pages
|