My Q&A Workorder database had an associated Lookup Table which translated nicely, as another form in the application.  Several factors make me want to split it out into it's own separate database:
1) My Invoice database will have its own, completely different lookup table, and
2) The fewer things "under the hood" that I have to show to my users, the better.

From what I've read, the procedure to do this seems to be:
1) Make a copy of the main application
2) Rename it to the Lookup Table's db name
3) Go into the new app and trim out every form/database except the lookup table
4) Go into the old app and trim out the Lookup Table.

Is this correct?  Or is there a better (cleaner/faster) way to do it?

If you are talking about the Lookup Tables in Q&A....

This should have come into Sesame as a database originally.....but....

You can use QA4LOOK.exe utility to extract a Lookup Table into an ASCII file. 
This is a utility provided with Q&A.

Then import that into a Sesame database.  Only need a Sesame form with 5 elements.

If you simply do not want the users to see that database then you can hide it using @HideTreeItem() found on page 122 of the Sesame 1.1 programming Guide. Just put it in the On Application Open Event.

-Ray

You might consider getting rid of the lookup table entirely and using GlobalValue instead. GlobalValues have a lot less overhead (read: "faster"), do not show up as a database in the command tree, and are much more flexible.

Infinity wrote on Aug 16^th, 2006 at 4:53pm:


GlobalValues are really very simple. They are a way to store a data using a tag. The tag is used to retrieve the data.

GlobalValue("MyName", "Mark")
 

Will store the string "Mark" under the tag "MyName". If I want to find out what is stored under "MyName":

var aa as string

  aa = @GlobalValue("MyName")
 

That's pretty much all there is to it. They are stored inside your application file, so they don't go away at the end of your session.

To lookup, lets say a zip code lookup by city and state, first store it:

var aa as string

  aa = CityName + "|" + StateName
  GlobalValue(aa, ZipCode)
 

And then look it up:

var aa as string
var MyZipResult as string

  aa = CityName + "|" + StateName
  MyZipResult = @GlobalValue(aa)
 

Usually a table of GlobalValues would be created once, often using a mass update. Then the normal event code would look things up.

Infinity wrote on Aug 17^th, 2006 at 4:32pm:


The data (its not really a table) is stored in the application file (.db and .dat).

Quote:


If you are trying to eliminate a lookup database, you would run a mass update on that database, moving the data into GlobalValues. Once that data is in Global Values, you don't need that database, or the code in the mass update again (accept as a backup).

Infinity wrote on Aug 17^th, 2006 at 8:54pm:


Even if they need to change occasionally, I would still recommend using GlobalValues. When you need to change some of them, write a 1 record mass update (don't affect the one record) that edits those Global Values to their updated value. When complete, you can probably just toss the code.