Arthur Fuller
fuller.artful at gmail.com
Tue Dec 27 11:01:16 CST 2011
This thread would appear to me to be about a subject addressed by my good friend Dejan Sunderic, in his books about SQL Server, which contained a chapter about inheriting databases. At the time it was a very novel idea, even though at that time I was well-acquainted with O-O software. Building on Dejan's lead, I investigated remodeling the modeldb database, and including a number of oft-used databases, and this has worked even better than I expected. In SQL Server, the core model is called modeldb. What I ended up doing was creating several different versions of this db, with names such as modeldb_OE (order entry), modeldb_COA (chart of accounts), etc. -- each based on modeldb but adding the tables of interest, so that simply by renaming a couple of dbs and then issuing a Create New I had a whole bunch of the core tables (transactions and lookups) instantly installed and populated and ready to go. Perhaps not an ideal solution, but it has worked for me. When doing an Access db, I do it manually, importing tables and forms and queries from databases whose content is isolated (e.g. Geography.mdb, CustomersAndOrders.mdb, COA.mdb), but the key to making this work coherently is precisely named, consistent columns in all the dbs -- it is always called CustomerID, OrderID, OrderDetailsID, ProductID, CategoryID, SupplierID, etc., and that never changes; may not need all of them, but it's all predefined in the inheritable databases and it's always consistent; that's the big trick). I haven't automated this, as JC wants his solution to work. If I'm "inheriting" from one Access db, say "CustomersAndOrders", it's incumbent upon me to remember to "inherit" all the tables and relevant queries and forms, and occasionally, modules. But force of habit causes few mistakes, and upon discovery of one, it's pretty easy to return and grab the missing object. Anyway, Happy New Year to everyone on this list! Arthur On Sun, Dec 25, 2011 at 9:44 AM, jwcolby <jwcolby at colbyconsulting.com>wrote: > William, > > What I am trying to do is have a shortcut open a program and keep it > invisible. That program copies a bunch of files, then opens a second > program, whereupon the first program shuts down. > > The shortcut properties invisible / minimized cause the first program to > never appear. The first program puts up a "working, be patient" splash > screen while it is opening the second program. > > Stuart's suggestion was to use the invisible / minimized properties of the > shortcut to cause the first program to not ever even be visible, which is > what I was after. > > > John W. Colby > Colby Consulting > > Reality is what refuses to go away > when you do not believe in it > > On 12/24/2011 4:49 PM, William Benson wrote: > >> I am asking how do you run a shortcut in code. Isn't john doing this with >> vba? >> >> TIA for answering my question so I can follow along. >> On Dec 24, 2011 4:44 PM, "jwcolby"<jwcolby@**colbyconsulting.com<jwcolby at colbyconsulting.com>> >> wrote: >> >> That worked perfectly Stuart. I set the shortcut visible attribute to >>> false and then set the Run Minimized attribute and I never even see the >>> CopyAndRun open. I now have a splash form that opens to say "be patient" >>> and off we go. >>> >>> John W. Colby >>> Colby Consulting >>> >> > -- > AccessD mailing list > AccessD at databaseadvisors.com > http://databaseadvisors.com/**mailman/listinfo/accessd<http://databaseadvisors.com/mailman/listinfo/accessd> > Website: http://www.databaseadvisors.**com<http://www.databaseadvisors.com> > -- Cell: 647.710.1314 Thirty spokes converge on a hub but it's the emptiness that makes a wheel work -- from the Daodejing