Jump to content

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

Recommended Posts

Posted

Greetings,

I am working on a database in which I am trying to use one table to provide a selection list for ease of data entry into another. The main table is a field work tracking system for a utility and the secondary table is a list of a few thousand streets that are in the service area. I have set up a relationship based on the first letter and have the match field in the primary table set up with a value list consisting of the alphabet so that when a user picks a letter, the portal below displays all the streets starting with that name. I then put a button on the portal row that executes a script to move the street name to the list of street names affected by whatever work is being done. The idea is to allow users to quickly and accurately enter data.

This works perfectly - except when you put it on the web. It seems that the web version is unable to recognise the portal row properly. To test this I added a step to get the current portal row and insert it into a global field so that I could see what was going on. This system works fine when running the system locally, but on the web, the portal number shows up as 0 the first time you click on a row, regardless of which row you select. Subsequent clicks begin to return the correct number and move the right data, although this did not occur until I put a step in the end of the script to commit the data.

Thanks in advance

Posted

I had problems with my portals, not exactly yours, but similar types of problems, and I was ripping my hair out. It turns out that just putting Commit Record at the end of your script isn't enough! I actually complained on the FileMaker web site, because a script that works fine locally, such as

Set Field ...

Perform Script ...

Commit Record

doesn't necessarily work right from the web, unless you add extra, unnecessary "Commit Records":

Set Field ...

Commit Record

Perform Script ...

Commit Record

See if adding a Commit after every block of Set Fields helps.

Also, see if calling Go To Record ( Get(RecordNumber)) helps, by refreshing the portals. It will make them snap, however (lose where they were scrolled to), which stinks.

This topic is 7508 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.