Simple autonumbering of a repeating field

[nedbguy]

Client of mine want a couple of fields to auto number themselves 1-40 each time a new record is started.

I have the repeating fields(Input, Split) set up and they are showing up as 40 vertical spaces but no numbers are appearing in them.

Any help would be most appreciated.

-Chris

[Kent Searight]

Create a global field with 40 repetitions, populate the repetitions with the values you want to populate your Input and Split fields, and make those fields auto-enter the value of the global field.

Why do you want 40 repetitions in your fields (if you don't mind me asking)?

[nedbguy]

He wants an editable sheet that is a grid. First two columns are to be numbered 1-40 automatically. The remaining five columns are text fields(also repeating) with descriptive info(Subsnake, Subject, Mic, Stand, and Notes).

The whole sheet is an input list template for a concert.

Example:

Input 1 is Split 1 Subsnake 1. Subject is Kick drum. Mic is D112. Stand is SOB(for short boom, round base), Notes is blank.

This layout is related to the particular event as they are all differant. Even the same artist performing in the same venue a year later will have a differant input list.

Hence the need for a printable list.

[Søren Dyhr]

Why do you want 40 repetitions in your fields (if you don't mind me asking)?

Yes when it could be say two portals of 20 related records in hardwired positions, when it comes to patching plans, are insertion of an extra sm57 underneath the snare sometimes required, or getting rid of linedrivers for keyboards - when the band suddently gets another keyboard player. This talks in direction of scripted manipulations of few portals contents, if it just isn't a replica of a spreadsheet.

--sd

[nedbguy]

He really is looking for more of a replica of a spreadsheet with simple editing and tabbing capability.

Question; Would the repetitive field idea or the 20 + 20 records idea be the simplest way to go?

[nedbguy]

To clarify further: I want to have a simple grid of 7 columns wide by 40 rows deep get the numbers 1-40 automatically appear

in the first two fields. All 7 of the fields are currently repeating fields on a layout that is related to the main layout.

Enders suggestion of a global field that has 40 repititions seems to be the way to go. However, I can't seem to get it to work.

Can someone step me through it?

[Ender]

Enders suggestion of a global field that has 40 repititions seems to be the way to go. However, I can't seem to get it to work.

Hey, keep me outta this one!

[nedbguy]

Sorry Ender. I meant Kent_S.

-Chris

[Kent Searight]

That wasn't exactly a suggestion about using 40 repetitions...you asked how to do it and I told you.

If you want my suggestion, then 2 things come to mind.

1. If you want something that looks, feels and acts like a spreadsheet, create an Excel document. Excel was designed specifically for that purpose.

2. If you want to collect and work with data in a flexible and meaningful manner, get rid of the repeating fields and create individual fields to hold data of each specific entity (subject, stand, notes, etc.). Then, instead of using repetitions for rows, create a record to create a row.

Hope this makes sense and helps.

[Søren Dyhr]

All 7 of the fields are currently repeating fields on a layout that is related to the main layout.

I have a principle, never ever to use repeating fields for storage of something a user can access directly, and only use them for utility purposes.

If you however insist on repeaters, why should you use autonumbering in the first place, when you in layoutmode can write the numbers directly on the layout next to the rows. Can't you be trusted in making such a sequence properly?

--sd

[comment]

That's what I was wondering about, too. Are these numbers ever going to change?

In any case, I believe the answer is create a selfjoin on constant1, and have the repeating field lookup the global repeating field thru this relationship.

[nedbguy]

The numbers in the Inputs column probably won't change but the numbers in Split will be changed dependant on the patch for that particular show.

[bruceR]

Get rid of the repeats.

[Kent Searight]

I'll second that...for the second time! :iagree:

[comment]

With respect, I don't agree. IIUC, this is a database of setups, and a single (atomic) setup is a snaphot of 40 parameters (or multiple groups of 40 parameters). A single parameter has no meaning on its own. The information in the repeating fields is not going to be used for searching or sorting. In fact, a database of pictures (with each picture showing the entire setup) would be equally functional.

Building a portal with 40 permanent slots would only add a complication, with absolutely nothing gained from it. Repeating fields seem like an ideal solution in this case.

[Kent Searight]

So why even use a database? Going back to my earlier suggestion, use Excel (or Lotus)spreadsheet if you want a spreadsheet.

Just because you can drive a nail with a screwdriver handle doesn't make it the right tool for the job. :tongue2:

[comment]

Why not, if it can do the job, and do it quite well? As I said, it IS a database. The question is, a database of what? Yes, he could make the setups in Excel. And then what? How is he going to find the setup used a year ago for a similar event?

Is it worth the trouble to go to Excel, create the setup, save it, insert it into a container - then after finding it, re-opening it an Excel, etc.? When all he needs is a couple of repeating fields to get the job done in one application?

I think the poster presented a legitimate problem, and he's not being helped by automatic responses that do not consider his particular situation.

[nedbguy]

Perhaps a file (see attached) demonstration is in order.

Client uses FM db as a way of tracking, quoting, contracting, and executing the shows he does(he is a sound reinforcement provider-think PA systems for music concerts and you'll get the idea). His solution is time sensitive(not for the equipment though) and consists of six related files(events, clients, venues, engineers, inventory, and itemsBid). One of the layouts that I created for him is called input list. On it are Artist(name of), Venue, Show date(s), Job number. Below is a simple text grid of 7 columns(Ch, Split, Sub, Subject, Mic, Stand, and Notes) on which he'll put the input and patch info for the particular show. There won't be more than 40 inputs per show(not at this point in time). He would like for the Ch(channel) and the Split columns to automatically be numbered 1-40 for him(saves time!), yet also be editable so as to reflect the needs of the show. Once he is done inputting his information, he can print this out and make copies for all the technicians involved.

So now you see why this has to be part of the db( LOVE FM!) and NOT a spreadsheet. Besides, I absolutely LOATHE Excel!

Best,

Chris

eventsinputlistexample.zip

[comment]

So why have you not yet implemented the auto-numbering?

[nedbguy]

Still trying to get it to work!

[comment]

Sheesh, I thought I gave you the answer in my first post:

Define a calculation field constant1 = 1

Define a relationship to the same file: constant1 = AllRecords::constant1

Define a global number field gIndex with 40 repetitions

Define your repeating fields to lookup AllRecords::gIndex

Fill the global with numbers 1 to 40, and you're done.

[nedbguy]

Remember, I am a novice here.

Define a calculation field constant1 = 1

Done

Define a relationship to the same file: constant1 = AllRecords::constant1

What do you mean by 'AllRecords'?

Define a global number field gIndex with 40 repetitions

Done

Define your repeating fields to lookup AllRecords::gIndex

Do you mean define it to lookup 'channel' via the above relationship?

Fill the global with numbers 1 to 40, and you're done.

How do I 'fill up' the global field?

Sorry for being such a novice at this!

-Chris

[bruceR]

Put get(calculationRepetitionNumber) in the first field then.

[comment]

"AllRecords" is the name of the relationship. The relationship is a self-join, meaning to the same file.

You fill up the global by typing the numbers 1 to 40 into its repetitions. You do this once, then any new record will lookup from the global.

I don't have version 6, but the attached v.4 sample might help.

RepeatLU.fp3.zip

[Søren Dyhr]

I was thinking, why lookup in the first place, if you prevent access to the field could it easily be the global couldn't it, and the size of the database be slightly smaller. By looking up the same value over and over is in my humble opinion storing redundant data.

As such has this thread more to do with eyeballing and graphical appearances, than anything else laid out by the author ...and the only reason for keeping it a filemaker solution is that the rest of the infomation system is made in filemaker and then ...silly obedience!

Perhaps it was a customers wink in the direction of making something usefull via the underlying database engine ...and by implementation of the suggested solution it equals a flunked exam proving something that could be hold against the developer as person later. It could be a test against faith and an encouragement to logical reasoning?

This is why there perhaps should be a hidden overhead be included, so lines could be grouped and reorganized in a more statistical manner more than repeating fields suggest and allows. I would not pursuade a screwdriver afficionado/snob into using a hammer for nails, although it's the image that comes to me.

I would merely suggest that the solution perhaps were better solved by approaching something like this:

http://previews.filemakermagazine.com/videos/513/DataTagging_full.mov

...which at least, is in the relational database realm! Compared to repeating fields which although being a charming companion in attempts to learn as little as possible, in the end could prove terrrible unflexible and would surprise no-one with their lack of virtues.

--sd

[bruceR]

Client of mine want a couple of fields to auto number themselves 1-40 each time a new record is started.

I have the repeating fields(Input, Split) set up and they are showing up as 40 vertical spaces but no numbers are appearing in them.

Any help would be most appreciated.

-Chris

Like I said - just use get(calculationRepetitionNumber) See attached.

Repeatz.zip

[Søren Dyhr]

Bruce he's on fm6

--sd

[nedbguy]

Exactly. Get(CalculationRepetitionNumber) doesn't work.

Plus, in Bruce's FMv.7 example, the autonumbering of the first column is not modifiable by the user.

Heeelllp!!

[Søren Dyhr]

I think you had the help availiable here, Comment gave you a solution which works!

If you need it to work in an allready created record issue a Relookup!

--sd

[nedbguy]

This is frustrating. Comments suggestion(s) are/have been helpful, but the file he sent I can not open so I can't see exactly what he's done. As stated, I am working in v6 which seems to make BruceR's suggestions in v7, not applicable.

I feel I am closer to getting this to work yet....so far.....

-Chris

[comment]

Drop the file (after unzipping) on the Filemaker application's icon.

[nedbguy]

THANKYOU!

I am all set now.

Thanks to all of you for all of your help!

Best,

-Chris

[Ohgo_Ohgo]

Ok whatever ;-)

included is the original file but with a small scripted loop which writes the Status (currentRepetitionNumber)in the Channel Field.

the trick is (old) to renumber Your field TAP order so You can go to the next field - the next repetition in this case.

just perform script "to input list" after You have created a new record

and please buy Yourself FMP 8 (that was horrible for me to go back . hahaha)

events93.1.fp5.zip

Edited January 23, 2006 by Guest
I am always late uhuuuuu