I don't know why it's not publising to the web like it should, but I'm concerned about your use of a "central server" and your statment that you "load the databae from teh centrial server".
How exactly are you doing this? It's possible that you are running a signficant risk of corrupting your database file here.
Well here I admit to not really being IT and figuring this out as I go.
But we have a server (called "central") on which we store many files in use by everyone in the (small, like dozen people) company. Most of these are administrative. But our database is also stored on this server. As I'm learning how to use filemaker I've been messing around with a copy I made and keep on desktop I'm using. This computer is the only one that anyone uses filemaker on. I would love to simply run it off this computer and keep a backup on the server (we also have a separate backup), but this is how it was when I got here and this is how they want to keep it, so *shrug* I'm stuck with what I have on that front.
That doesn't fully answer my question.
When users want to open this file, do they go directly to a shared directory on the server and open it or do they use Open Remote to access it on a computer where FileMaker Pro first opens and hosts the file?
If they are directly opening the file from a shared directory on the server, they are taking a serious and avoidable risk that the file will be corrupted. Said corruption "might" even explain the problems you are having, thought usually such damage will show up in other more obvious ways.
ah i see what you're saying. yes i was taught to open it by going to the shared directory and opening it directly, not accessing it through the "open remote". i'm pretty sure there are other problems (crashes when trying to export to excel), but short of reconstructing the database entirely I'm not sure what to do about it.
You have a people problem and a file integrity problem. I can't help you with the people problem. It's up to you to work with your colleagues to change this process or any fixes we come up with will be undone by future file corruption.
First, you need to check your file for corruption:
Pull a copy onto your machine, launch FileMaker without opening the file and then select Recover from the File menu. Select your file, run the recover and see what is reported.
Things to keep in mind about Recover:
- Recover does not detect all problems
- Recover doesn't always fix all problems correctly
- Best Practice is to never put a recovered copy back into regular use or development. Instead, replace the damaged file with an undamaged back up copy if this is at all possible. You may have to save a clone of the back up copy and import all data from your recovered copy to get a working copy with the most up to date information possible.
If this file turns out to be damaged and you do not have an undamaged backup copy (If you have back up copies they will also need to be checked with a recover to see if they are also damaged), you may need to rebuild your file--which can be a major undertaking.
(thank you for your help and patience)
I pulled off a copy and ran recover, it poped up a window saying it had recovered x number of files (the correct number for the number of records i have) and found no other damaged areas. but it's still not working, even off the recovered local copy.
when i look up the error in the computer this is what it shows me:
Library not loaded: @executable_path/../Frameworks/FMEngine.framework/Versions/A/FMEngine Referenced from: /Applications/FileMaker Pro 8.5/Extensions/Web Support/FM Web Publishing.app/Contents/MacOS/FM Web Publishing Reason: unsafe use of @executable_path in /Applications/FileMaker Pro 8.5/Extensions/Web Support/FM Web Publishing.app/Contents/MacOS/FM Web Publishing with restricted binary
if that helps
nevermind, just found Question about FM Server 8 and New Mac OS and i'm also running osx 10.6 so i guess this isn't my fault but still isn't going to work. :]
thank you for your help and patience!
i'm still not sure why it worked once, but whatever, at least i can go to the higher ups and say this aint gonna happen.