dbTalk Databases Forums  

New Record Request (Slow)

comp.databases.filemaker comp.databases.filemaker


Discuss New Record Request (Slow) in the comp.databases.filemaker forum.



Reply
 
Thread Tools Display Modes
  #1  
Old   
jc@agncs.com
 
Posts: n/a

Default New Record Request (Slow) - 06-02-2007 , 11:31 AM






Running FM 8.0 over a WAN. The first time I run a simple script of
"New Record Request" it takes about a minute. After that it runs
fine. No summary fields on the layout. I have even tried running the
script on a "blank" layout and gotten the same results.

Thanks


Reply With Quote
  #2  
Old   
d-42
 
Posts: n/a

Default Re: New Record Request (Slow) - 06-04-2007 , 01:46 AM






On Jun 2, 9:31 am, j... (AT) agncs (DOT) com wrote:
Quote:
Running FM 8.0 over a WAN. The first time I run a simple script of
"New Record Request" it takes about a minute. After that it runs
fine. No summary fields on the layout. I have even tried running the
script on a "blank" layout and gotten the same results.

Thanks
Take a look at your field definitions, and check for validation
constraints. e.g. if you are forcing a field to be unique that could
dramatically slow the new record creation down. (And it may cache the
results, allowing the next run to go quickly.)

Or, if the field def's do auto-enter calcs or lookups on related files
FM may have to open those related files, and once open, subsequent
runs can go quickly.

-regards,
Dave



Reply With Quote
  #3  
Old   
jc@agncs.com
 
Posts: n/a

Default Re: New Record Request (Slow) - 06-04-2007 , 09:07 AM



On Jun 4, 2:46 am, d-42 <db.pors... (AT) gmail (DOT) com> wrote:
Quote:
On Jun 2, 9:31 am, j... (AT) agncs (DOT) com wrote:

Running FM 8.0 over a WAN. The first time I run a simple script of
"New Record Request" it takes about a minute. After that it runs
fine. No summary fields on the layout. I have even tried running the
script on a "blank" layout and gotten the same results.

Thanks

Take a look at your field definitions, and check for validation
constraints. e.g. if you are forcing a field to be unique that could
dramatically slow the new record creation down. (And it may cache the
results, allowing the next run to go quickly.)

Or, if the field def's do auto-enter calcs or lookups on related files
FM may have to open those related files, and once open, subsequent
runs can go quickly.

-regards,
Dave
Dave:

Thanks for that, it seems logical that is whats going on since I am
guilty of both mentioned above.

thanks



Reply With Quote
Reply




Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is On
HTML code is Off



Powered by vBulletin Version 3.5.3
Copyright ©2000 - 2012, Jelsoft Enterprises Ltd.