Auto saving changes to layouts

[rob]

Why sometimes when I make a change in the graph or definitions and when I leave, does it say it is making changes to the layouts and it seems to go through every layout in my file even if it isn't even related to a table I changed?  It is very slow.  And it says I can skip it but it gives no indication of what it will mean if I skip it.  It is very unfriendly with no message and no way to look up in help what it even means.

 

Can someone tell me what it is doing and what it means if I skip it?  And if wrong place my apology.  It seems to happen when I access remotely and I wasn't sure if that might be why it is asking me.  Even idea of what it is called so I can search?  It isn't 'saving layouts' or anything similar that I can find.  Thank you for reading.

[rob]

I posted in layouts here http://fmforums.com/forum/topic/89277-auto-saving-changes-to-layouts/

 

but I realize it might be an issue which happens when I access the file remotely so I thought I should put it in server section here.  It didn't do it when I had the files on my desktop but it does it when I access it served on world cloud.  It is very time-consuming when it goes through every single layout just because I change one small thing in definition.

 

Please if anyone knows what it means and is it safe to SKIP it and what happens if I DO skip it?  I would have moved the post myself but I could not figure out how to do it.  Thank you so much.

 

[webko]

It's checking whether your change *could* have an effect on anything else.

 

It does this locally too, but it's a lot faster.

 

Personally, I'd never skip this, even when I know it's not going to have an effect on any layout - just let FM do its thing I reckon...

[GisMo]

What do you mean by one small change? Delete a field from a table? Usually Filemaker is going to calculate what will be affected and then prompt you. SKIP, will bypass any warning and just do what you're trying to do. If you're 100% comfortable with your change, then press skip.

 

How long is long? Seconds? Minutes? I say just let it do it's thing and be patient. Most normal changes shouldn't take that long to save.

[rob]

Thank you, webko, I appreciate it.  I got a response here also http://fmforums.com/forum/topic/89282-saving-changes-to-every-single-layout/

 

If I change the index on InvoiceType to minimal, why does it need to go to layouts which aren't even connected to Invoices?  It goes through all of my layouts one by one.  It would make sense if it went through all invoice layouts but it goes to table layouts without an invoice field at all.

 

What does it do on these layouts?  It would make sense if I changed a field name and it wanted to see if it needed to change the field names on layouts but my changes aren't layout based at all.  I would think File Maker is smart enough to know when to check all layouts and when not to.  Even I know that an index change wouldn't affect the layouts. Or would it?

 

On World Cloud, and with 140 layouts, every time I leave definitions it takes several minutes to go through them all.  And these are all changes which should not affect skema from what I understand.  So I do not understand.

 

I just read another post about being wrong to double post.  I am hoping Lee doesn't spot this or I'll be in trouble. I won't do it in future.  Now I have to go back to the other post and explain what I already explained here.  Or I guess I'll just point to this one again.  Now it makes sense why not to double post though.

[rob]

Thank you, GisMo, I don't mean SKIP as in saying OK to field dialog - I mean the dialog which says it is going through every layout in the file checking it.  I responded on the other thread also.  I am surprised that FileMaker isn't smart enough to know which changes might affect a layout (layout labels is the only think I can think of).

 

How long?  It seems longer when you are waiting for it but it still is terribly long when I am trying to design in it.  It takes probably 1-2 minutes every time.  It is on world cloud server.  It has only a handful of records in separation but it has 100+ layouts with probably 25 tables.

 

Your input is greatly appreciated.  I guess I'll just live with it.  I wondered if I skipped all of that while working, if I could then force FM to DO THEM ALL when I am done instead.  I assume it might be important (although if I change an index I can't imagine how it would matter) but I am afraid it won't ever do whatever it needed to do.

 

Without knowing what it does and why it does it, I cannot even predict if it will synchronise those needs later if I skip them while designing.  Why give the option to skip?  Skip what? And if I skip now, can 'whatever it needs to do' be ran later?