1 pointHello This is a tricky one, but I think could be improved by design in the database. FM will only attempt to locate the other files if it needs to. You could have layouts for use in FM Go that don't have any fields, references or scripts that require the other databases. Then FM Go won't bother to open them if it never needs the data. The other technique might be to use Global Variables in the Manage->External Data Sources. In your startup script you could set those Globals to the correct values if you are on a computer, and set them to nothing if you are running in iOS. This would prevent Filemaker from looking for them. However, if your database relies on values from the other files for calculated fields or layout items that you need to display on iOS then both of these techniques will have the effect of reducing functionality in your database. Maybe that helps?
This leaderboard is set to Los Angeles/GMT-07:00