I'm going to murder my DB, please help!

[ddreese]

I'm getting so unbelivably frustrated over here.

I'm running FM Server 5.5 with FM Pro 6 to work on it. I also have developer, but rarely use it. The problem I've been having is I have been making changes to scripts so they work properly (it's mostly for navigational purposes), and after I fix them, they go one as if I have never fixed them in the first place. I seriously don't know what's going on, and I'm ready to start punching stuff. I end up fixing the same scripts literally every few hours, and it's unbelievably annoying. What the $#@$ is going on?:

Should I stop the FM server and work on the files directly from the server??? ahhhhhhhhhhhh!

[leahbrooks]

What kind of script step changes are you making?

You may want to close the file (using the server admin) and open it locally, make the changes, and then re-serve it.

Is there a possibility that you have two (identically named) copies of the file, and one is served and one is not?

[ddreese]

Most of my script changes are navigational, like I said before. For instance, I'm setting a global field called g_navigationalorigin in my login file so that whenever I move into another file to add/edit/etc. a record, it keeps track of where I came from. Therefore when I hit the 'ok' or 'back' button, what have you, it takes me to the section of the website I was at before.

I don't think there are multiple files being shared, there seems to be only one of each file in the dir that I have them in.

I was thinking that shutting off the server software and making changes might work, but I won't be able to do that anymore when the database is actually being used (right now I'm developing it). I was hoping there was some dumb thing that I'm not doing correctly that negates the changes I've been making. Thank you for the reply, my database thanks you, you bought it a precious few minutes of time before being beaten!

[Anatoli]

I bet you are writing to other files.

There is absolutely no exemption from rule number 1: never ever have 2 databases with the same name on the server, some other machine or local machine.

[ddreese]

You know, I bet you are right. I have similar files on my computer that I'm working on it, but how does FM know they are there? I have a start file pointing to the hosts IP, and whenever I perform and external script I always hit the hosts button to browse to the file that has the script, and it will say "Perform script (external:case_notexxx.xxx.xxx.xxx)" or something like that. Then when I got back, the xxx.xxx.xxx.xxx is missing until I do it again. Do I completely remove this files from my machine, or what???

[Ugo DI LUCA]

Yep,

Not served, other folder name, other file names (v2,v3,), zipped....or you'll get in big trouble.

[ddreese]

Thanks guys, I'll hide those puppies. Am I the only one that thinks this is the dumbest thing ever? I should have posted earlier before I got really upset, hahaha... Serenity now!

[edit]

Oh yea, have a nice weekend everyone!

[Ugo DI LUCA]

IMO, who would say it never happened to him while developping the db is a GREAT lyer.

[ernst]

It's a lady canine.

When I'm in my office I do have quit a lot of networked computers -also running Filemaker- at hand so I can quickly check if there's only ONE computer serving all databases by checking the 'Open Host' dialog on the computer next to mine.

But I've been tricked by this as well. Renaming, like Ugo suggests, is IMO indeed the best way to deal with this.

Ernst

[Anatoli]

RE: When I'm in my office I do have quit a lot of networked computers -also running Filemaker- at hand so I can quickly check if there's only ONE computer serving all databases by checking the 'Open Host' dialog on the computer next to mine.

That works but if some leftovers are on local machine and not set to multi-user, one must be really careful.

Ideal -- almost -- is FM Developer where you can rename files as you wish and Relations and Scripts are also checked.

The only problem is, when files are served from different points, but that is rare (and bad) practice.

[ernst]

>>That works but if some leftovers are on local machine and not set to >>multi-user, one must be really careful.

Had not thought of that, Anatoli, very good point!

Regards,

Ernst

[Anatoli]

Hihi, that was MY mistake some years ago

[AudioFreak]

I have had users make copies of databases to keep on their desktop. At one point I selected open hosts and to my amazement my purchasing database was being hosted by 3 different computers. Talk about confused.

"That works but if some leftovers are on local machine and not set to >>multi-user, one must be really careful". Very good point!

This bit me in the butt due to users thinking they are using the "live" database but are actually working on a copy and then telling me the changes they are making are not being saved. I gave classes and explained how everything was working, and last but not least "Use the OPEN HOSTS ONLY to get to the file you want"

[Anatoli]

RE: I gave classes and explained how everything was working, and last but not least "Use the OPEN HOSTS ONLY to get to the file you want"

This doesn't guarantee, that local databases will not be opened The first will be probably open from the server, but then anything can and will happen. Scripts and relations will open the first one FM will find.

[AudioFreak]

This was mainly a problem when we were not using filemaker server and the databases were on individual computers. My simple point was that a little communication and education can go a log way.

[Anatoli]

That is very good point. No doubt about it