Tina Norris Fields
tinanfields at torchlake.com
Fri Apr 4 10:20:43 CDT 2008
Hi All, In order to just get my client's database functional - not perfected, just functional - so they can record contributions and send out acknowledgement letters, I did install a VM (using VMWare Server) and load it with Win98 (with second edition update), then I installed as much of Office 97 as I needed (Access and Word, essentially). About the only problems I really had with that are: 1) it is slow to work in, 2) the screen resolution is awful, and 3) it won't see my USB ports, so I couldn't use my flash drive or my USB-connected printer (I installed it and had the print feature print to a file, because I just needed to be able to preview my reports, not really print them). For the future, I have to learn a lot more about this virtual machine business. Working in that environment I succeeded in creating a new blank database and importing into it the functional portions of my client's Version9 and Version10 databases. The data tables of Version10 were whole and properly related, but many of the forms and reports were corrupted, as well as a few queries. Pulling what worked from each of the database versions I was able to get Version11 to work nicely, and I tested the mail merge Word letter. It works. One nice little extra is that I fixed a detail that bothered me. The form letter had a field for the honorary prefix (Mr., Ms., Dr., etc.) before the field for the first name, which is great except when there is no honorary prefix used. When that happens, the resulting name line starts with a space. I know, it's a tiny detail, and it can be quickly fixed with a little search and replace action, but, I'm very picky!. So, I put in a conditional mergefield, which I knew could be done, but which I hadn't done since Word was a DOS program (yes, I AM that old), and it took me a while to sort it all out, but I got it and it works, and I'm delighted. Next steps with this client include revisiting how they want to use the database - there are features in it that haven't been used since 1999 when they moved their accounting to QuickBooks, for instance - and remodeling it. Part of the remodeling will include splitting the database into BE and FE, an area where I have only a little experience so I'll be back for help. Furthermore, I have to put more security measures in place than are there. It is very clear that someone has been fooling around in the database, writing small queries with useful names like Query1, and changing table names (without updating the queries that depend on those tables) - stuff like that. Someone knows enough to get into the database objects, but not enough to keep from doing damage. My friend who built the database back in 1997, took the executive director at his word that nobody would mess with the innards of the database. Ha! Thanks for all the help I received from the members of this list. Tina