Yes, there is caching that's being done. Whenever you open a database, FileMaker performs a series of caching operations on the Relationships Graph. It goes through the graph and parses out all the tables, joins, etc. If it's accessing external files, then it has to process the credentials to get into those other files, as well as the normal process. Depending on the size of the graph, number of joins, and network speed (you mentioned that this other database is on a second server on the open Internet), it's entirely normal for there to be a significant pause.
Thank You Mike for the quick reply ...
Yes this helps ... It confirms what I "Felt" was going on ... I can explain it to the users ....
An initial delay over the internet makes sense, but not each time you modify
3,500 records is tiny. How many Mb is that ? How many fields ? is the opening layout huge ?
Have you defined any other external data sources ?
Try Pinging the external IP address, and check the latency
> I can duplicate the pause by trying to use database manager, or modifying a field.
> The second database resides on another server, running FMP 12 Server and is accessed via the internet.
There isn't much latency .... ~19ms
The pause only occurs once per session after opening the database.
The modifying the field was through editting the layout. If I have experienced the pause once then there is not any further pauses.