Global dilemma

[dulux]

Hi again,

I understand that $$ creates a global value. I have a script that sets a global value and then opens each layout (separate tables for each) in turn and adds a new record to it, populating a matched field with the contents of the global. at least that is what it is supposed to do. It works perfectly on the first layout it goes to, and after that the global field is not populating the table field as indicated. The text is identical, save the table name and this leads me to suspect it's the global at fault. I shouldn't have to reset the global value at every step so the next fields can use it should I?

Cheers

[dreamingmind]

Are you getting a record locking problem? You may have to commit each record as you go along.

Without more info, it's a little hard to guess. At a minimum, what result are you seeing on the 'wrong' attempts?

[dulux]

It's wierd. I am trying to pass each record only the Learner ID number which is a matched field. The first table to get a record gets this number, but the subsequent tables do not. However, they DO get the learner name, something they would only have access to if the matched field in the table correlated with the one in the learner table that I am sending the information from.

Very odd. No records are locking.

[dreamingmind]

That sounds a bit like there is a look-up or calculation acting on the field.

Do you get the same result when you do the process manually rather than through the script?

Don

[dulux]

Nope - nothing like that. The tables are all linked by Learner ID alone, and the layouts have the fields drawn from the Learner Table (which is the main one). If the Learner ID field is empty in the other table, it shouldn't be able to access and display the guys name, right? Is it somehow using the global I created with $$learnerID to do this instead?

Alas, there is no manual method of performing this action without me writing one as it is all script based.

**Update** I need slapping. The layout was not linking the field to the correct one and so was empty. I have since corrected this and all is as it should be. Thanks.

Edited September 22, 2008 by Guest

[dreamingmind]

I'm suggesting you:

manually go to layout 1

manually enter your value

manually go to layout 2

manually enter your value

then do you still get the goofy result?

or perhaps you're script is doing MUCH MORE than this. in that case more info and examination of the intervening processes would be in order.

Don

[bruceR]

Hi again,

I understand that $$ creates a global value. I have a script that sets a global value and then opens each layout (separate tables for each) in turn and adds a new record to it, populating a matched field with the contents of the global. at least that is what it is supposed to do. It works perfectly on the first layout it goes to, and after that the global field is not populating the table field as indicated. The text is identical, save the table name and this leads me to suspect it's the global at fault. I shouldn't have to reset the global value at every step so the next fields can use it should I?

Cheers

Not enough information.

Post your script or example file.