Jump to content

This topic is 7492 days old. Please don't post here. Open a new topic instead.

Recommended Posts

Posted

Is it possible to only IWP one database? I can turn on IWP in the preferences which makes them all display, but ideally I would like only one particular one to be available.

Basically can I IWP on a "per database" basis?

Any help greatly appreciated

  • Newbies
Posted

Hi

I have the same question. i have two files say, Interface and Data File. One contains all the tables (Data File)and the other has all the layouts,scripts and relationships (Interface).

Thus on the web , i host only one of them (the one having all the layouts : Interface).

The issues that I have in this arrangement are in the scripts. The Go to Related Record script step (in Interface File), shows a Unknown Layout to be selected.....even though there is a layout mentioned. This issue cud be b'coz the file in which the script is made has no table of its own. Though the script performs its function.The problem lies in the display, in Scriptmaker...it shows an unknown layout. When all the stuff is in one file, everything works perfect.

Cud someone help me in keeping my data and my layouts separate (on the web)??

Thnx

Smitha

Posted

In response to simonr's question,

Yes it is possible to do this. When you enable the Web Companion under the Application Preferences 'Plug-ins' tab, you enable the Web Companion for your instance of FileMaker.

However, if you go to File->Sharing, you can Uncheck the Web Companion box for any file that you do not want shared over the web. The Sharing options are unique to each database.

All you need to do is goto File->Sharing and uncheck the Web Companion for each database that you do not wish to share. Any database that you do wish to share, just leave it checked.

Cheers,

Jonathan

Posted

"In response to simonr's question,

Yes it is possible to do this."

I believe that may depend upon the version of FMP. Pre 7 yes. But I understand from readibg these forums that Web Companion does not exist in 7.

To smitha, and anyone else running ScriptMaker. I am the web expert with ScriptMaker. Here is my advice to you. ScriptMaker handles one event at a time and does not queue subsequently made, near-simultaneous requests for script events, at least in Pre 7. AFAIK version 7 is a step backwards in publishing Pro db's on the www. No custom (CDML) allowed. So that means you are stuck with IWP. And also, in line with the step backwards, I do not know for a certainty, but I would wager that FMI has NOT resolved the single-thread issue of ScriptMaker. The upshot of this is you think the "script performs its function", and it well may for a single user. And if the website you are developing is for a single user then you need not worry. But if there are to be (hopefully) many users then you need to rigorously test your scripts from a minimum of six browsers in a near-simultaneous fashion and see if there are any conflicts which would cause any script event to fail (not perform). Whatever you are using you need to confirm that if an event is not processed the results page reflects that failure (I bet it won't).

I am the only one who has worked around the problem in CWP pre 7. IWP in pre 7 was not very good and I never used it. But with the ScriptMaker problem in CWP, it had to exist in pre 7 IWP since the problem is caused by the single-thread event handling nature of the beast. And with the backward step in web publishing and FMI's position papers on web publishing (you did read those before you bought the product), it is 99.9% certain that FMI has not resolved the single-thread issue of ScriptMaker in 7, and has no such intentions. Too costly and they really don't want developers to get around the licensing of shared db files by using a single server version via browsers (LAN or WAN).

Good luck with the problems you have purchased. You may find you need to consider pre 7 and CWP. Except for hiding data (security) in non-web accessible files, ScriptMaker is unnecessary pre 7 with CWP.

Just wait till you tie-up the db file with a looping ScriptMaker event and deny access to all others until the event completes. Ha, ha, ha, ha, ha.

This topic is 7492 days old. Please don't post here. Open a new topic instead.

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.