[AccessD] Strange Access Behavior

ewaldt at gdls.com ewaldt at gdls.com
Mon Apr 24 08:24:29 CDT 2006


Well, duh. I do have a module that runs a lot of SQL statements, so I turn
off warnings at the beginning of it. I don't remember doing so, but I'll
bet I ran it and it was interrupted for some reason, so that warnings were
not turned back on. In that case, rebooting Access would, of course, reset
warnings to their default ON position.

Pretty sure this is it. Sorry to waste everyone's time. Well, if my
explanation above helps someone, then I guess it wasn't a total waste. If
you experience what I was complaining about, you might consider just
creating a simple macro that turns warnings on. You can then run that
whenever the problem shows up, and then see if it is corrected.

Thomas F. Ewald
FCS Database Manager
General Dynamics Land Systems
(586) 276-1256





                                                                           
             "Gary Kjos"                                                   
             <garykjos at gmail.c                                             
             om>                                                        To 
                                       "Access Developers discussion and   
             04/24/2006 08:39          problem solving"                    
             AM                        <accessd at databaseadvisors.com>      
                                                                        cc 
                                       ewaldt at gdls.com                     
                                                                   Subject 
                                       Re: [AccessD] Strange Access        
                                       Behavior                            
                                                                           
                                                                           
                                                                           
                                                                           
                                                                           
                                                                           




I've have had similar weirdness like this happen although I haven't
used the autoform or new object thingies. Closing and restarting
Access is my usual procedure when I encounter unexplained oddities
like that. If I really want to be sure it's not something lurking I
reboot. Then if it still happens I go digging more. The restarts
usually fix me up though. If nothing else it gives me a couple minutes
to reboot my brain too.

GK

On 4/24/06, ewaldt at gdls.com <ewaldt at gdls.com> wrote:
> All right...more confusion. We all know that Access saves data
> automatically. Now, however, it also saves object changes automatically.
> That is, I make a change to a table in design view, then close design
view.
> Access has always asked me if I wanted to save my changes. It does not do
> that now; it automatically saves the changes. I don't see anywhere that I
> could have set this as an option; has anyone else experienced this? Any
> suggestions as to how to get out of it?
>
> TIA.
>
> Thomas F. Ewald
> FCS Database Manager
> General Dynamics Land Systems
> (586) 276-1256
>
>
>
>
>
>
>             Thomas F
>             Ewald/LS/GDYN
>                                                                        To
>             04/24/2006 07:03          accessd at databaseadvisors.com
>             AM                                                         cc
>
>                                                                   Subject
>                                       Strange Access Behavior(Document
>                                       link: Thomas F Ewald)
>
>
>
>
>
>
>
>
>
> Hitting the New Object:AutoForm button when a table or query is selected
> creates the form, as always. However, it will not let me get out of it
> without saving. If I don't want to keep it, I have to save the dumb thing
> and then delete it. Could I have accidentally set something to do this?
Is
> anyone else experiencing this? Using the New Object button was always a
> quick way toto create a temporary form, but you had the option to just
not
> save the puppy. BTW, I'm using XP (Access and Windows).
>
> TIA.
>
> Thomas F. Ewald
> FCS Database Manager
> General Dynamics Land Systems
> (586) 276-1256
>
>
>
>
> --
> AccessD mailing list
> AccessD at databaseadvisors.com
> http://databaseadvisors.com/mailman/listinfo/accessd
> Website: http://www.databaseadvisors.com
>


--
Gary Kjos
garykjos at gmail.com





More information about the AccessD mailing list