Yes, I want to update data from this view.  Once the user has their subset
of records, they want to be able to edit them and save changes.  That's why I thought this was a perfect candidate for a SQL VIEW.  (And a great time for me to learn about them...)

I've now discovered another problem with the syntax I posted.  Once I got rid
of the bad WHERE clause, I still an error until I changed from:

SELECT t1.*, t2.Descr, t3.Name ;
    FROM Table t1, Codes t2, Names t3 ;
    WHERE t2.PrimKey = t1.ForKey1 AND t3.PrimKey = t1.ForKey2

to:

SELECT * FROM Table2 ;
	RIGHT OUTER JOIN Table1 ;
		ON Table2.PrimKey = Table1.ForKey1 ;
	LEFT OUTER JOIN Table3 ;
		ON Table3.PrimKey = Table1.ForKey2

(identifier names changed for clarity).

Setting a FILTER after CREATEing and USEing the SQL VIEW seems to work OK, but I'm working on a small test data set right now.  Performance might be unnacceptable in live system.

This is easier than FPW 2.6, right?  ;)

Thanks,
Rich

Rich Addison, Micro Vane, Inc., Kalamazoo, MI
Relax, don't worry, have a homebrew.
  - Charlie Papazian, The New Complete Joy of Home Brewing