Rocky Smolin - Beach Access Software
bchacc at san.rr.com
Sat Apr 22 13:00:50 CDT 2006
I had that problem as well. Can't remember how I got around it. Do you have Jet 4.0 SP8 installed? http://office.microsoft.com/en-au/assistance/HA011225981033.aspx#180 Rocky John Colby wrote: > N0, I couldn't set it to low. There is no "Security" choice under Tools / > macro. > > PITA really! > > > John W. Colby > www.ColbyConsulting.com > > > -----Original Message----- > From: accessd-bounces at databaseadvisors.com > [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Rocky Smolin - > Beach Access Software > Sent: Saturday, April 22, 2006 10:56 AM > To: Access Developers discussion and problem solving > Subject: Re: [AccessD] Project is unviewable > > Wow. Lowest setting and you're still getting the nag message about unsafe > expressions, etc.(we're talking Tools-->Macro-->Security-->Low, right?)? > Could it have to do with that particular db? What if you create a fresh db. > Does it happen to that one as well? > > Rocky > > > John Colby wrote: > >> I tried that and it flat did not work. >> >> >> John W. Colby >> www.ColbyConsulting.com >> >> >> -----Original Message----- >> From: accessd-bounces at databaseadvisors.com >> [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Rocky >> Smolin - Beach Access Software >> Sent: Friday, April 21, 2006 7:17 PM >> To: Access Developers discussion and problem solving >> Subject: Re: [AccessD] Project is unviewable >> >> John: >> >> I got rid of that crap by lowering my security setting in Access. But >> you may not want to do that. >> >> Rocky >> >> >> John Colby wrote: >> >> >>> Has anyone ever gotten this? >>> >>> I was trying to get rid of the 2003 crap that forces you to answer >>> THREE questions correctly before it allows you to open an Access >>> database. In the process I created a digital signature and applied >>> it to the database. Not sure exactly what went wrong but now "the >>> project is unviewable" which means NO CODE CAN BE SEEN!!! >>> >>> I googled the error message and is appears (though not directly >>> stated) that this is a known bug with a workaround... which doesn't >>> work >>> >>> >> around it. >> >> >>> Has anyone ever successfully recovered your code from this specific >>> piece of hell that MS is subjecting me to? >>> >>> John W. Colby >>> www.ColbyConsulting.com >>> >>> >>> >>> >>> >> -- >> Rocky Smolin >> Beach Access Software >> 858-259-4334 >> www.e-z-mrp.com >> >> -- >> AccessD mailing list >> AccessD at databaseadvisors.com >> http://databaseadvisors.com/mailman/listinfo/accessd >> Website: http://www.databaseadvisors.com >> >> >> > > -- > Rocky Smolin > Beach Access Software > 858-259-4334 > www.e-z-mrp.com > > -- > AccessD mailing list > AccessD at databaseadvisors.com > http://databaseadvisors.com/mailman/listinfo/accessd > Website: http://www.databaseadvisors.com > > -- Rocky Smolin Beach Access Software 858-259-4334 www.e-z-mrp.com