|
|
Using Global Fields Help
I've been posting for help on how to use Global fields because I want a
user to be able to type in data into a form without having to do a new
record add. Using global fields I can see that I can do that but I
don't know how to get those entries into a different table ?
I've tried using the Record Committ but nothing seems to happen, I'm
not really sure what exactly that is. But I have about 5 global fields
that when a user goes to a form they fill out and I want to move that
data into another table and delete the global values.
What has been happening is that a user sees what the previous user
entered into the global fields because the data is still there.
-S
|
|
0
|
|
|
|
Reply
|
squeed2000 (117)
|
2/19/2005 3:45:30 PM |
|
You have very acurately discribed what a global field does. A global is not
intended for entering and keeping data, but for storing general data, for
instance when you are inside a script to remember from which layout you
came. Or for a counter, but NOT for entering data you want to keep using.
Global fields retain their value for ALL records. You have to make a new
record each time you want to store something new, and use normal fields for
it. I have large databases containing over 500000 (five hunderd thousend)
records. This is normal.
Ursus
<squeed2000@yahoo.com> schreef in bericht
news:1108827930.456027.253490@z14g2000cwz.googlegroups.com...
> I've been posting for help on how to use Global fields because I want a
> user to be able to type in data into a form without having to do a new
> record add. Using global fields I can see that I can do that but I
> don't know how to get those entries into a different table ?
>
> I've tried using the Record Committ but nothing seems to happen, I'm
> not really sure what exactly that is. But I have about 5 global fields
> that when a user goes to a form they fill out and I want to move that
> data into another table and delete the global values.
>
> What has been happening is that a user sees what the previous user
> entered into the global fields because the data is still there.
>
> -S
>
|
|
0
|
|
|
|
Reply
|
ursus
|
2/19/2005 4:57:05 PM
|
|
One way or another, someone is going to have to click a button to do
something. They can add a record and then type data directly into the
record. Or they can type into a global and click a button that runs a
script that creates a new record, moves data from each global field to a
real field and then clears the global for the next entry.
Globals only show the data that the current user has entered. If you're
seeing other data from other users, then each user must be opening it in
single user mode, entering their data and closing. In this case the
next single user who opens will see that data in the globals.
The Commit Record script step is a way of commiting the fields to a
record (not globals because globals don't belong to a record) without
switchng records or clicking outside a record. Until a record is
committed, it can be reverted to what it was before the changes.
squeed2000@yahoo.com wrote:
> I've been posting for help on how to use Global fields because I want a
> user to be able to type in data into a form without having to do a new
> record add. Using global fields I can see that I can do that but I
> don't know how to get those entries into a different table ?
>
> I've tried using the Record Committ but nothing seems to happen, I'm
> not really sure what exactly that is. But I have about 5 global fields
> that when a user goes to a form they fill out and I want to move that
> data into another table and delete the global values.
>
> What has been happening is that a user sees what the previous user
> entered into the global fields because the data is still there.
>
> -S
>
--
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Howard Schlossberg (818) 883-2846
FM Pro Solutions Los Angeles, California
FileMaker 7 Certified Developer
Associate Member, FileMaker Solutions Alliance
|
|
0
|
|
|
|
Reply
|
Howard
|
2/19/2005 5:45:08 PM
|
|
<squeed2000@yahoo.com> a �crit dans le message de news:
1108827930.456027.253490@z14g2000cwz.googlegroups.com...
> I've been posting for help on how to use Global fields because I want a
> user to be able to type in data into a form without having to do a new
> record add. Using global fields I can see that I can do that but I
> don't know how to get those entries into a different table ?
>
Hello,
I'm not very familiar with Filemaker 7, but this should be simple and
similar to previous versions.
You need a script to create the new record in the "target" table:
New Record
Set field (field_a, entryform::global_field_a)
Set field (field_b, entryform::global_field_b)
etc.
- In filemaker 7, I suppose that you have to specify the table at some point
- From what I've read, you don't need to define a relationship to access
globals. Maybe you need a add a "table occurence", though, especially if you
want to access globals in other files.
You can then clear the form with:
Set field (global_field_a, "")
Set field (global_field_b, "")
etc.
You can attach this script to a "Submit" button on the entry form. If your
entry form is in a different file, then of course you will need a script in
that file to trigger the other one.
HTH
Marc-Andr� Paiement
> I've tried using the Record Committ but nothing seems to happen, I'm
> not really sure what exactly that is. But I have about 5 global fields
> that when a user goes to a form they fill out and I want to move that
> data into another table and delete the global values.
>
> What has been happening is that a user sees what the previous user
> entered into the global fields because the data is still there.
>
> -S
>
|
|
0
|
|
|
|
Reply
|
Marc
|
2/19/2005 6:07:41 PM
|
|
|
3 Replies
363 Views
(page loaded in 0.057 seconds)
|
|
|
|
|
|
|
|
|