Related Data Lookup from External FM Database fails in IWP

[Agent Ska]

On a single host, I have two shared databases. Both of which are open and running.

One of the databases has a value that looks up the related data from the other database. Within a filemaker client, the lookup works beautifully.

If I try to call the same data, from IWP however, the lookup fails. Is there a way to force the remote lookup to work in IWP? (a script step, perhaps?)

[IdealData]

Possibly you didn't switch IWP access on in the second file.

Have a look at the the sharing set up for IWP - watch out for the users that can access it too as this can be restricted to privilege sets.

Also the privilege set for the IWP user(s) must also have the IWP extended privilege enabled.

[Agent Ska]

Currently, the only user that is accessing it is me and I am signed on with full-access priveleges. And, not sure that it should matter or not, but it is the same user & password for both databases.

Both databases are shared via IWP and filemaker network.

[Søren Dyhr]

Read this , or page 658-659 in:

http://my.safaribooksonline.com/0789735121/pref01#X2ludGVybmFsX1NlY3Rpb25Db250ZW50P3htbGlkPTA3ODk3MzUxMjEvY2gyMWxldjFzZWMz

...the chapter about lookups and filtered portals!

--sd

[Agent Ska]

Read this

Funny, I had seen this topic before posting, but did not see your response listed for some reason. Odd.

Anyway, my local lookups are working great, it is simply the lookup to the external database.

, or page 658-659 in:

http://my.safaribooksonline.com/0789735121/pref01#X2ludGVybmFsX1NlY3Rpb25Db250ZW50P3htbGlkPTA3ODk3MzUxMjEvY2gyMWxldjFzZWMz

...the chapter about lookups and filtered portals!

That's alot of exclamation points. I don't have that book in my library - I have "The Missing Manual."

Edited January 6, 2009 by Guest

[Søren Dyhr]

Well you seem to have a looser definition of lookups than the filemaker discourse, where it's a type under autoenter and not live linking...

IdealData's reply must be the fitting one then.

--sd

[Agent Ska]

Ok, so I registered for the Safari books and read the chapter and it still didn't exactly help... even if I force a commit record to happen after entering the information necessary for the lookup, the lookup does not happen.

Again, all local lookups happen without issue. It is the lookup to the external data that is not happening.

[Agent Ska]

Well you seem to have a looser definition of lookups than the filemaker discourse, where it's a type under autoenter and not live linking...

IdealData's reply must be the fitting one then.

--sd

Not at all. The field in question is defined as a lookup and I am attaching a screenshot illustrating that fact.

[IdealData]

Please re-read my posting earlier.

Before you question whether your lookups work you must have the database set up in such a way for the IWP privilege to be enabled on the user account.

The default "Admin" account (Full Access) DOES NOT have IWP enabled by default - nor any of the other EXTENDED privileges

[Agent Ska]

Please re-read my posting earlier.

Before you question whether your lookups work you must have the database set up in such a way for the IWP privilege to be enabled on the user account.

The default "Admin" account (Full Access) DOES NOT have IWP enabled by default - nor any of the other EXTENDED privileges

Ok, I have re-read and doubled back and checked everything.

IWP access is definitely enabled for both databases.

The user is not the default "Admin" account, but a userX account. The User does have full access rights, and also in the extended privileges the fmiwp and fmapp sets are enabled.

[Søren Dyhr]

You haven't told us why the lookups are required at all?

Here's some considerations to make:

http://filemakerlayouts.blogspot.com/2008/12/filemaker-killing-lookup.html

...it's actually some time ago I stopped using the oldfasion way, simply because we have found it slower in our IWP solutions.

--sd

[Agent Ska]

One database is an order entry system used for selling Art.

The other database is used for cataloging the art.

In the Order Entry screen, the user types in the artID, and the Description is then looked-up from the catalog of art. (This portion is also scripted from the customer's layout for easy re-ordering - which is primarily how it would be used in the IWP solution).

The lookup, and subsequently, the "Calculated lookup" work fine in the Filemaker client, but not in the IWP Solution.

Edited January 6, 2009 by Guest

[Søren Dyhr]

Why are these in two files, there seems no logical reason for doing so. Please expand here!

The next issue I don't get is why it's a lookup at all, why have versions of the same data, in both tables? Is a description something that gradually changes over time, and if so why?

--sd

[Agent Ska]

It seemed cleaner to keep them as separated databases. One is an image database. The other is a financial database.

How else would the Art Description be called onto a Worktag/Invoice if not by a lookup?

No, the description does not change over time.

[Søren Dyhr]

If the description doesn't change is there no need to copy it anywhere, try to look at this movie to see how filemaker as tool deals with referential integrity:

http://www.filemakermagazine.com/videos/graph-rules-four-rules-to-remember.html

It's certainly not a lookup, but a live relation you need - why should the description be treated like a historic fact that might inflate/deflate over time?

Invoicing usually goes this way:

http://www.filemakerpros.com/joinprint.zip

...where it is obvious which of the data is a recorded snapshot of the pricelevel for the item at the invoicing moment.

Regarding the neatness should you study the separation model, and have all data in one file, and if you need distinctive files as browsers of the data make them as needs turn up.

http://www.newcenturydata.com/downloads/separation_demo.zip

--sd

[IdealData]

Ok, I have re-read and doubled back and checked everything.

IWP access is definitely enabled for both databases.

The user is not the default "Admin" account, but a userX account. The User does have full access rights, and also in the extended privileges the fmiwp and fmapp sets are enabled.

Mmm...

Any chance you can post some zipped up clones?

[Agent Ska]

Thank you both for the suggestions.

Søren, I think I am going to combine the data. I love the separation model you posted - that is indeed a very interesting tactic.

I think I was keeping the data separated because of a belief that production information and accounting information need not exist in the same place for security reasons. However, there are enough security parameters in Filemaker that, I suppose, blows that concept out of the water. Plus the information was going to exist on the same server anyway.

Again, thank you for the suggestions and the educational links.

[Søren Dyhr]

As a kind of checking question, would I like you to tell when to use lookups and when not to, in your own words? The separation model might be neat, but if you not yet makes clear distinction between live relations and lookup ... do we need to apply diffferent tactics!

--sd

[Agent Ska]

Sorry. Not sure that I am following you here.

[Søren Dyhr]

What is lookups in the filemaker context made for, if referential integrity supposingly is the goal?

--sd