editing a script that automatically closes after running...

[RadioactiveFrog]

Hello,

I have a script that someone else wrote and it is written to auto close after running. This sounds like a silly question but i have not been able to figure it out for myself.

How do i go about opening the page so i can view and edit the script?

Many Thanks,

RF

[Lee Smith]

Hi RF,

I hesitate to say this, but when reading this question, and the one you posted a second plea for help this morning in, that you need more help than you can expect from a forum. I think the best solution for you would be to hire FileMaker expert to fix the files, or contact the author/developer of these files and insist upon their support. I don't know what kind of a contract you had with the that developer, but they are in the best position to help you.

To be honest with you, I'm concerned that you don't have enough knowledge or ability of FileMaker to work on these files. Although the support by this Forum can be excellent, it is expected that you posses some knowledge of FileMaker when you post. If you are going to be the "in house" FileMaker guru, you need to enroll in some few FileMaker classes. Without a good working knowledge of FileMaker, your attempt to work on these files will be long agonizing experience for all involved.

Also, I'm concerned that you might be making changes that will end up mucking up the works.

Lee

[RadioactiveFrog]

Thanks for the reply Lee,

I understand where you are coming from. I am getting there with FileMaker and it is only a overview of the system that i need at this time. Not to become a guru! But anyway as you feel i am asking too much i will leave it.

Regards,

RF

[Lee Smith]

It's not a question of you asking too much, it is a question of knowing what you are effecting by making these changes.

My observance of your situation is as follows:

Your files are currently being used, and have been for awhile.

Someone, maybe you, maybe your boss, wants some changes to the files, either because they are not working in their mind as expected, or they don't do things the way it is felt that they should.

The developer involved in producing this set of files, is not responding to request for changes.

No one on staff is verse in FileMaker, and you have been selected to fix them.

Here are the problems that I see.

There are often good reasons that a developer stops responding and/or supporting their files.

       Can't collect the money they are already Owed.

       Can never satisfy the clint (gave up)

       Contract dispute

       Client decides they don't need the developer anymore, taking over support in house.

       Project is complete and performs to everyone's satisfaction.

Making changes to an existing solution can be problematic, and unless you are familiar with the files, and know what the heck you are doing, you can do more harm, than good.

Without knowing what the developer had intended for things to work, and why they set things up they way they did, there is a chance that you can muck thing up, instead of improving things.

Lee

[RadioactiveFrog]

My observance of your situation is as follows:

Your files are currently being used, and have been for awhile.

Someone, maybe you, maybe your boss, wants some changes to the files, either because they are not working in their mind as expected, or they don't do things the way it is felt that they should.

The developer involved in producing this set of files, is not responding to request for changes.

No one on staff is verse in FileMaker, and you have been selected to fix them.

Yes that is about right!

Here are the problems that I see.

There are often good reasons that a developer stops responding and/or supporting their files.

Can't collect the money they are already Owed.

Can never satisfy the clint (gave up)

Contract dispute

Client decides they don't need the developer anymore, taking over support in house.

Project is complete and performs to everyone's satisfaction.

well, none of those are actually true! We could do with the assistance but they don't seem to want to help. I guess they are just too busy with other work. This is an old project of theirs and maybe they feel modifying it would take too long as they initially provided no documentation!

Making changes to an existing solution can be problematic, and unless you are familiar with the files, and know what the heck you are doing, you can do more harm, than good.

Without knowing what the developer had intended for things to work, and why they set things up they way they did, there is a chance that you can muck thing up, instead of improving things.

i am working on a dummy copy of the live one so i won't break the working version !!

Yes, trying to figure out what the developer did is proving to be a nightmare! But at the moment i don't see an alternative

Thanks for your reply,

RF

[stanley]

RF:

Even for an experienced developer, it can be a nightmare to untangle another developer's work - especially when there is no documentation. I don't envy your position, trying to learn FMP by delving int a completed, undocumented solution.

Having said that, if you can provide a bit more detail regarding the problem, it's possible that we can open the door for you. In your original post, it sounded like what was happening was that a script was firing another script in a second file. That file opens, runs a script, and then closes. You have no way of seeing what is going on. Something like that?

You can always try to kill a script while it is running (on your development duplicate ONLY!) On the Mac it is command-. but I can't recall the key combo on Windows.

-Stanley

[flapjacks]

I can't even untangle my work easily. Do yourself a favor and hire a good FMP person. If you don't and you screw something up it will leave you with a solution that dosn't work along with your current problem. I can't tell you how much grief I have caused myself. Listen to the voice of experience. I wrote my entire solution first in 5 then in 7. I have been at it for 10 years at least.

John

[RadioactiveFrog]

thanks guys,

i found that if i held esc down then i could view the script! Might not be the best way but it worked!

Yes i am going to have to discuss this with collegues and my boss as it doesn't look like it is a viable solution having me fix it!

thanks,

rf

[RadioactiveFrog]

There are often good reasons that a developer stops responding and/or supporting their files.

Can't collect the money they are already Owed.

Can never satisfy the clint (gave up)

Contract dispute

Client decides they don't need the developer anymore, taking over support in house.

Project is complete and performs to everyone's satisfaction.

I think we have discoverd why we are not getting much response out of the company that built the system in teh first place!! The guy who worte it is no longer with them! : and with no documentation for something that was written 3-4 years ago...no wonder they can't be bothered!!

still frustrating for us tho.

[Lee Smith]

Hey, there's a new one for my list. :

It looks like you need to hire an experienced FM developer to take over this project. Why not post a want ad in the help needed topic area.

Lee

[stanley]

RF:

I agree with Lee. At the very least, you should get someone to survey your solution and put together a rough documentation for you.

-Stanley

[RadioactiveFrog]

thanks guys, as much as i would like to do that right now it is not an option ! ho hum...