InfoVeg

It may be possible to reduce the file size by ~10MB by importing all objects into another fresh db. This had problems the first time I tried it, in that once a lot of objects went missing mysteriously (not a good sing) and another time the SQL of queries got rewritten such that it wasn't clear if the SQL was still OK or not (at least one query failed because it couldn't figure out a join).

To tackle the SQL issue, a list of queries with SQL should be made, including rowSource for combo boxes and list boxes. Once that is done, then SQL can be checked, and, when needed, fixed.

My notes:
--delete sections (code, macros, forms, queries, tables) then c&r and see what happens to file size
--this done, and db was still 13MB after all deleted. Trying to import into new.
queries are "recompiled" when importing. This caused at least one query to fail (vmd stuff, due to join not working)
done: cvsEntry_v223p0306_importedAllObj3 --copied SQL from original, still some different, but length of SQL always thte same, so likely just ordering of clauses. Nothing added, nothing removed.
THIS HAD ERRORS in query (SQL changed) and so we need to create a registry of queries and SQL before attempting this.