FMP4: Saving global field over network? Alternatives? 
Author Message
 FMP4: Saving global field over network? Alternatives?

Hi all. I've got a global field which gradually increments as a
quasi-serial number type of thing (a script increments it by one at
certain times, but not for every record). The value then gets copied into
an ID number field. This works well on one machine.

However when I wanted to network this database it all crashed down around
my ears. As the Help says 'Only the hosts changes are saved with the
file'. Why on earth would this be? It seems a rather pointless limitation.
And are there some common ways around this? (forcing the global value to
update somehow?)

A standard auto-enter serial number is no good, as when numbers are
duplicated the serial number ticks over twice and you end up skipping
numbers. Auto-enter previous value is no good, records are created all
over the place. A maximum summary field is no good as with over 35000
records it takes quite a while to summarize things. Any other
thoughts/ideas that I've missed?

Thanks very much for any help you may be able to provide.

Regards,
Andrew Wright.



Wed, 07 Mar 2001 03:00:00 GMT
 FMP4: Saving global field over network? Alternatives?

Quote:

> Hi all. I've got a global field which gradually increments as a
> quasi-serial number type of thing (a script increments it by one at
> certain times, but not for every record). The value then gets copied into
> an ID number field. This works well on one machine.

> However when I wanted to network this database it all crashed down around
> my ears. As the Help says 'Only the hosts changes are saved with the
> file'. Why on earth would this be? It seems a rather pointless limitation.
> And are there some common ways around this? (forcing the global value to
> update somehow?)

> A standard auto-enter serial number is no good, as when numbers are
> duplicated the serial number ticks over twice and you end up skipping
> numbers. Auto-enter previous value is no good, records are created all
> over the place. A maximum summary field is no good as with over 35000
> records it takes quite a while to summarize things. Any other
> thoughts/ideas that I've missed?

Global fields were designed this way for specific reasons. In a
networked file the global value cannot be changed by guests, this allows
a default value to be restored on every login, utilized in guest
operations and then restored again. VERY useful for things like password
schemes and other functions too numerous to mention.

In your case, of course, the global field design doesn't meet your
needs. Neither does keeping a regular field to increment in your main
database. The solution is simple, a regular text or number field used to
contain the highest value assigned lives in its OWN DB. Since not every
record in the main DB gets an assigned serial value, you need to set a
script to read that field, copy the value into the current record and
increment the field by one, ready and waiting for the next user, from
somewhere on the network, to access it.  This field will be the
authority, and will change and store the changes permanently.  Relate
the two by a constant value (like a "1") stored in a global in the main
and a simple text field in the small standalone DB. (I think that works,
globals in relations are a little wonky.)

Just need to think a little outside the global. ;)  Good luck.

Lynn Allen
Allen & Allen Semiotics         FSA Member - Filemaker Pro Consulting
http://www.semiotics.com        Web & Graphic Design



Wed, 07 Mar 2001 03:00:00 GMT
 FMP4: Saving global field over network? Alternatives?
You can use a calculation that determines the maximum serial number from
http://www.filemakerpros.com (called "serial numbers" in the Tips and Tricks
section) and your auto enter serial number would be the calculation + 1. It
may be slow but probably faster then the script or the summary field.

Hope this will help!

Quote:

> Hi all. I've got a global field which gradually increments as a
> quasi-serial number type of thing (a script increments it by one at
> certain times, but not for every record). The value then gets copied into
> an ID number field. This works well on one machine.

> However when I wanted to network this database it all crashed down around
> my ears. As the Help says 'Only the hosts changes are saved with the
> file'. Why on earth would this be? It seems a rather pointless limitation.
> And are there some common ways around this? (forcing the global value to
> update somehow?)

> A standard auto-enter serial number is no good, as when numbers are
> duplicated the serial number ticks over twice and you end up skipping
> numbers. Auto-enter previous value is no good, records are created all
> over the place. A maximum summary field is no good as with over 35000
> records it takes quite a while to summarize things. Any other
> thoughts/ideas that I've missed?

> Thanks very much for any help you may be able to provide.

> Regards,
> Andrew Wright.



Thu, 08 Mar 2001 03:00:00 GMT
 
 [ 3 post ] 

 Relevant Pages 

1. Alternative To Global Field IN Web Database

2. Global field does not update through networked database

3. Global field behaviour over network

4. Global fields over a network

5. FMP4 cache, temp file, saving

6. save fmp5 to fmp4

7. How global are global fields

8. Multi-user/network question FMP4

9. Help understanding FMP4 Networking

10. FMP4: networking

11. save objects to database or save object fields

12. REPOST: save objects to database or save object fields


 
Powered by phpBB® Forum Software