[AccessD] properties

John:

I've had this happen before, with A97, A2k and A2003.  I thought
originally it was just A97...and I still have no clue as to why it does
it.  Just occasionally it won't replace the original...the computer is
having a "bit phart" or something.  Any time that it happens, I throw out
both the original I was working on (hopefully backed up... before the
compact/repair) and what it generated and start the process over with a
fresh copy.  I close out of Access (whatever version I was using at the
time...) and sometimes, reboot the computer I was on before trying it
again.  By doing this, I've not run into what you've described because
I've not kept the 'questionable' copy.  And that's exactly why I do all of
this so I don't have the app in some condition that's questionable.

As for 'remoting in', ummm, hmmm, "I use RDC to connect ..."...:) that way
I don't add any new words to the English language...and it doesn't NEED
any new ones...LOL.

Greg Smith
gregsmith at starband.net

> Hello John,
>  Does your code in anyway manipulate those properties during runtime,
> and if
> so, does your code check for the property state at the forms start up?
>
>  I say this because when your move to design mode, and make changes and
> save
> the form, the new property settings have a habit of getting saved also.
>
> I run into this situation often.
>
> Robert Gracie
>
> -----Original Message-----
> From: accessd-bounces at databaseadvisors.com
> [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of John W. Colby
> Sent: Tuesday, November 23, 2004 9:24 PM
> To: 'Access Developers discussion and problem solving'
> Subject: [AccessD] properties
>
> I had a strange occurrence last night and I just wanted to check the
> list to see if anyone has ever seen such a thing.
>
> Windows XP / Office XP, I remoted in to a client site and started work
> on a FE.  At some point I tried to compact / repair the db and got the
> old error message that "the database could be renamed" and the copy was
> saved to db2. I saved the original and then renamed db2 and continued
> work.  I did NOT test editing / adding records etc.  The client was
> asked to test the changes and came back very upset that two entire tabs
> of the form were "locked".  I remoted in tonight and started poking
> around and sure enough all the subforms (controls) on those two tabs
> have the enabled property set to no which prevents even setting the
> focus into the subform.  Further all of the "allow
> edits/deletions/additions" are set to no for the actual subforms
> themselves.
>
> My conjecture is that something happened at the point Access tried to
> close the database to do the compact/repair or when it attempted to
> delete the original and rename the compacted copy.  Given the damage
> I've found so far I certainly don't trust the copy to continue work on.
> Who knows what else has been changed.
>
> Has anyone ever seen such a thing happen?  I never have, but there are
> so many properties changed that I have to think that Access somehow set
> these properties at some point.
>
> John W. Colby
> www.ColbyConsulting.com
>
> Contribute your unused CPU cycles to a good cause:
> http://folding.stanford.edu/
>
>
> --
> _______________________________________________
> AccessD mailing list
> AccessD at databaseadvisors.com
> http://databaseadvisors.com/mailman/listinfo/accessd
> Website: http://www.databaseadvisors.com
>
> --
> _______________________________________________
> AccessD mailing list
> AccessD at databaseadvisors.com
> http://databaseadvisors.com/mailman/listinfo/accessd
> Website: http://www.databaseadvisors.com