I have recently done a data separation on a solution, essentially I took the original file, duplicated it, renamed it and changed all file references to point to the existing file as the data source, so that the new file can enter data into the existing database. Why? Because the new file had a whole heap of layout changes made to it and I did not want to disrupt the existing solution (live production system).
All seemed to be going well... at least on the desktops anyway. All iOS devices accessing the new file via WAN (3G) are lagging. If you open the original files, all is well. No problems.
The file references are relative, so is this the problem? Should the file references be set to an IP address path to the original file? If I do this, what happens to the desktops on the LAN?
Anyone know why it might be slower on the iOS devices? NOTE: The initial connection to the host is using a domain name (not IP address), this works fine for the orginal file, but when the new file is launched, thus referencing the old file, things slow down, is this a DNS issue? Any clues, hints suggestions are welcomed.
Please also note that the new layouts are CLEANER than the ones in the old file - they are fairly simplistic
.... and the performance via a desktop (via WAN) is a little slower on the new file as apposed to the old file. Is there a difference is scripts between old and new? Not a lot, if anything the newer one is again, a little 'cleaner'.