Jim Lawrence
accessd at shaw.ca
Mon Mar 28 11:04:22 CDT 2011
Hi Janet: If the tables are within the application they must be hidden as a different named object. Check to see if all objects are being displayed (tools > options > view). Another trick is the move the database so far off the viewing area that it is no longer visible...check as far right as possible. You can try and force the database to expose itself by attempting to link to it by running the link-manager etc... Check to see if there is an autoexec macro that does obscuring when the DB is opened and then the Unhide command is turned off or the windows display can be turned off via a API call...Anything can be done once a autoexec macro is run. Go into Tools > startup and make sure the option "Display Database window" is checked. It is most likely one of these tricks to hide or obscure the database as getting too fancy with renaming can crash the system. One thing to check is if the Disable Shift Key option have been invoked so just holding down the shift key when opening the DB will not allow you to gain access to the DB before the autoexec macro is run. There are a number of little apps out there that can toggle this feature off and on. This of course is just the tip of the proverbial iceberg as there can be all sorts of protection schemes within the code to monitor changes in an objects properties. Some developers spend almost as long writing protection as writing the app and it can take even an experienced programmer a couple of hours to remove. HTH Jim -----Original Message----- From: accessd-bounces at databaseadvisors.com [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Janet Erbach Sent: Monday, March 28, 2011 8:12 AM To: Access Developers discussion and problem solving Subject: [AccessD] 'Hidden' form question & Excel 2010 question Hello - I have 2 questions for you all. 1) We use a pre-packaged access application for order processing: I've created a number of custom forms and modules that I export to a 'customizations' data base and import into the main app whenever I install it to a new machine. I have one form that seems to export successfully - I get no error messages, anyway - but when I open up my 'customizations' data base it can't be found. I've checked to see if it was somehow set to be hidden, and that's not the case either. I tried exporting it to a temporary data base, and it appeared there just fine. But I need it to go into this 'customizations' data base, and it just won't go! What could be causing this? 2) Do any of you have any experience writing VB code for Excel 2010? A tech temp agency in our area is looking for someone with that kind of experience for a specific project; if any of you are game for that type of thing, please let me know. Thank you! Janet Erbach IT/Office Manager Natural Healthy Concepts www.naturalhealthyconcepts.com 920.886.7500 * 866.505.7501 -- AccessD mailing list AccessD at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/accessd Website: http://www.databaseadvisors.com