Re: automatic field creation


Well, I'm not a cardiologist, but I did have a heart attack and a
bypass operation last year, does that count?

I am very sorry about that, did not intend joke in any way,
I apologize.



If you're having problems with speed of display, having many calculated
fields on the screen is most likely the cause. Simply displaying 300
or 600 plain number fields will not cause slowness, but displaying
summary fields or calculations, particularly ones dependent on related
fields, will bring a db to its knees.

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 ?


One solution is to enter all the base data, and then have a script that
contains the necessary calculations use Set Field to establish all the
calculated values. Those fields then become non-calculated number
fields and will display, sort, and summarize very quickly when
reporting or moving from record to record.

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...)

is that correct ?


You can also do a great deal with auto-enter calculations in number
fields if you don't want to use a script. These also display quickly,
but sometimes need help triggering when new values are entered. In this
case the functions Let and Evaluate are your friends.

I am not used to those functions but I am ready to get new friends : )

--
Lynn Allen

Thank you very much !

Diego

.

Relevant Pages

  • RE: Requery on command button not working
    ... Are these calculations coming from "across the ... See http://www.QBuilt.com for all your database needs. ... >> The CPU is busy executing your request. ... >>> buttons the intention is to display the releveant data for that period. ...
    (microsoft.public.access.forms)
  • Re: Insert a future date
    ... on systems that are configured to display dates formatted as d/MM/yyyy ... all positive and negative delay values now calculate to the correct ... > MemoDate happens to always merge the current date. ... > get it to work properly I'll know I can perform date calculations on any ...
    (microsoft.public.word.mailmerge.fields)
  • Re: Insert a future date
    ... > coded to work on systems that are configured to display dates ... >> perform date calculations on any other dates pulled from our DB). ... The list below shows my output with various negative delay ... >> If I restore the MemoDate mergefield from Line 3 and try a sampling ...
    (microsoft.public.word.mailmerge.fields)
  • Re: automatic field creation
    ... Simply displaying 300 or 600 plain number fields will not cause slowness, but displaying summary fields or calculations, particularly ones dependent on related fields, will bring a db to its knees. ... One solution is to enter all the base data, and then have a script that contains the necessary calculations use Set Field to establish all the calculated values. ... Those fields then become non-calculated number fields and will display, sort, and summarize very quickly when reporting or moving from record to record. ...
    (comp.databases.filemaker)
  • Re: Split an action and run on the servers
    ... I have a method which fetches information from ... I do some calculations based on the ... the data into multiple blocks and run separately on different servers. ... the calculation is done merge the results and display back it to the user. ...
    (microsoft.public.dotnet.languages.csharp)