What's the best/easiest way to get data (in this case, a list of names) from two separate tables (same file) into a single alphabetized list?

RDecker

The Troi Text Plug-in. http://www.troi.com

It has all the functions you need to do this.

Is there no way to do this within FM7?!

My situation doesn't allow for the purchase of add-ons/plug-ins; this is a solution that will be provided at no cost in run time format to several small non-profits...

RDecker

Are the names static or will you be adding/editing them?

The indiv names would normally be static (though if someone got married, they could change). There will be names constantly added to both tables, however.

RDecker

Please sprinkle "I think" through this. Haven't tried it in V7 and memory is a bit shakey.

Define two valuelists for each of your two fields.

Define a AllNames = ValueListItems(dbname1, Field1 List) & para thingie & ValueLitItems(dbname2, Field2 List)

Define NewValList as values from the field AllNames. (Not sure if it can be a Global.)

Thanks. Two weeks ago I'd have tried your idea. But since I couldn't figure it out then, and no one else had any ideas, I restructured the database so that what I had in two separate tables previously are now together. That created other problems in my situation, but I was able to work around those issues easier than my original.

RD

if the two tables are related in some way, u can make an unique id on both tables, and then on the third table where u wish the combined list to be, an ID field to identify.

then what u do is to use auto-enter of calculated results... i am a bit lost here but i have done it using this method, or step-script would do too.

be patient... and use ur brain, it took me some time to figure out a way too.

or use money to save ur extra brain work and time :-)

Combining the two tables is the right idea. Since both tables were dealing with people, then they really were holding a lot of the same data. Any extra data they held that they didn't share could be in another table and related to the People table.

It's a bit more object-oriented way of doing things, and it helps in a lot of situations. Creating a list is one, finding is another.

I agree with spankalee. It is usually not worthwhile to have two tables with the same data.