AngeloM

John, I'm not at home so I can't exactly test, but ... You should be able to put the in/out times into two fields as the full h:m:s and use the difference for the calculation of that part. The frames would probably be best left seperately and then you could have a field for the format. Then, to calculate the difference, you subtract the frame values using the correct value based on the format and, if the difference is < 0, you would borrow 1 second (or x frames) from the time. The calc may look pretty busy in the calculation field with different if clauses and such, but it should be very easy to do.

John, I'd have to agree. Maybe the "published" page is just an intro type page and the button (or whatever) that the user clicks on to "enter" the site would perform the find. Is that what you were thinking too?

Ellen, the color problem I'm not too sure about unless the color/screen resolution that you have selected is too low compared to what you had on the PC side. As for the fonts, what sizes are you using? There are default settings under the system preferences that tell the system how to display fonts of certain sizes - specifically, small sizes will generally not display very nicely. Try selecting a different font and size for one or two of the screens and see if it improves. If so, then the Arial may not be transferring properly. Even though they are the same name, fonts are still the one thing that everyone seems to have problems when doing cross platform stuff. PCs are typically using TTF (True Type Fonts) while the Mac is moving to OTF (Open Type Font). You can look these up on Adobe's web site for more info. Unfortunately, I'm at work now and not at my Mac or I'd be able to give you a better idea where the font preferences are. I'll check this again when I get home and see if you've gotten any better help from some of the other people here.

Okay. I've never done web sharing with FM on either platform so I can't specifically address that. However, I do know that you can create a script that will perform a find and have it run that script at startup of the db. Wouldn't there be a similar function (i.e. to have a script run automatically) when the db is opened via the web? If so, then you can manually perform the find, create a script to go to whichever layout you need to display via the browser, perform the find without a dialogue box and viola. I'm sure the related file would work but I think it's just a lot of work to go through to get it done and, as John pointed out, the maintenance of that related file (since it is actually a lookup not a true related file) would be tedious.

Local dbs are in users:shared:ST_HD_Data Users are all logged in with admin privs (didn't want to but thought that might be causing the problem).

I did try it with the checkbox on and off. Same results. I even set up the IP of the server in the hosts list and re-established all the relationships and script steps that call external scripts while I was logged in as the admin (admin of the db - machine login is admin as well).

I searched through the forum and did not find anything for this. Here's the skinny: Small FM app (20 dbs) being served on FMS 5.5v2, Beige G3, OSX 10.1.5. Desktop running FMP 6.0v4. There are also 8 local dbs. Links were set for these files to point back to the host machine. They do not appear to be saved as everytime the user signs on, they are asked to locate the dbs. Manually going in with the admin PW and re-establishing the links in the scripts and relationships does not help either. This db system has been running (with upgrades) for 9+ years and this never happened prior to OSX. Previously, when a change was made, the link would have to be re-established but it would remember it the next time. Any ideas? Thanks! Angelo