[AccessD] Remoting In (was: properties)

Andy,

We talked about how flexible the English language is during the 'English
or Spanish or Something' discussion.  

<grin>

Dan

-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Andy Lacey
Sent: Wednesday, November 24, 2004 7:19 AM
To: Access Developers discussion and problem solving
Subject: RE: [AccessD] Remoting In (was: properties)

Jeez what's this new verb "to remote in"? How does that decline? I
remote
in, he remoted in, he/she/it will have been remoted in.... What's wromg
with
using real words? ....grumble, grumble, grumble. Right, I'm going to
keyboard out of this email.

--
Andy Lacey
http://www.minstersystems.co.uk



--------- Original Message --------
From: Access Developers discussion and problem solving
<accessd at databaseadvisors.com>
To: 'Access Developers discussion and problem solving'
<accessd at databaseadvisors.com>
Subject: RE: [AccessD] Remoting In (was: properties)
Date: 24/11/04 14:10

>
> John,
>
> What mechanism or method do you use to remote in to a client's site?
> I'm struggling with this now.
>
> Does anyone have recommendations or warnings about what works and what
> doesn't?
>
> Thanks!
> Dan Waters
> ProMation Systems
>
>
>
> -----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 8: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
>
>
>
>
>
>

________________________________________________
Message sent using UebiMiau 2.7.2

-- 
_______________________________________________
AccessD mailing list
AccessD at databaseadvisors.com
http://databaseadvisors.com/mailman/listinfo/accessd
Website: http://www.databaseadvisors.com