[AccessD] Changing Table Names

 > ...how many times has MS claimed an Access bug was "fixed" only to find out later that it wasn't 
or the "fix" introduced a new problem

Such a cynic...

;)

John W. Colby
www.ColbyConsulting.com


William Hindman wrote:
> ...how many times has MS claimed an Access bug was "fixed" only to find out 
> later that it wasn't or the "fix" introduced a new problem ...I have AC 
> turned off and use F&R instead ...I used to much prefer Speed Ferret from 
> Black Moshannon but they've not updated it past 2002 ...shame that :(
> 
> William
> 
> --------------------------------------------------
> From: "Charlotte Foust" <cfoust at infostatsystems.com>
> Sent: Thursday, March 05, 2009 1:10 PM
> To: "Access Developers discussion and problem solving" 
> <accessd at databaseadvisors.com>
> Subject: Re: [AccessD] Changing Table Names
> 
>> Name AutoCorrect was a disaster in 2000 and has been regarded with
>> suspicion every since, but I don't know how much of that is holdover
>> from the original problems and how much has actually been tested.  Like
>> all such "features" Microsoft provides, it can be a two-edged sword,
>> even if it not longer corrupts databases.  I generally made of habit of
>> turning off all the helpful default settings and only turning on the
>> ones I really wanted.
>>
>> Charlotte Foust
>>
>> -----Original Message-----
>> From: accessd-bounces at databaseadvisors.com
>> [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of jwcolby
>> Sent: Thursday, March 05, 2009 9:52 AM
>> To: Access Developers discussion and problem solving
>> Subject: Re: [AccessD] Changing Table Names
>>
>> Big concern on the corruption??
>>
>> Back when it came out there were horror stories with the feature so we
>> all just kinda quite using it.  It is on by default IIRC when you create
>> a new db and I have left it on by mistake.  I have never had it bite me,
>> in fact I marveled at how well it worked.
>>
>> That is a useful feature for their target market, the "power user".
>> AFAICT it still exists clear out in 2007 so perhaps MS spent the time to
>> fix the bugs.
>>
>> AFAIK neither it nor Rick's Find and Replace change the name of tables
>> or fields out in the BE from inside of the FE.  I could be wrong though.
>>
>> John W. Colby
>> www.ColbyConsulting.com
>>
>>
>> Keith Williamson wrote:
>>> Well...I'm the only one using it...so that part isn't a concern.  But,
>>> certainly, I don't want to corrupt it.   :)   My application is fairly
>>> simple....mostly just queries that churn and burn data from our SQL
>>> accounting application.  Big concern on the corruption??
>>>
>>> Keith Williamson | Associate, Asst. Controller | kwilliamson at rtkl.com
>>>
>>> RTKL Associates Inc. | 901 South Bond St. | Baltimore, MD  21231
>>>
>>> 410.537.6098 Direct | 410.276.4232 Fax | www.rtkl.com
>>>
>>>
>>> -----Original Message-----
>>> From: accessd-bounces at databaseadvisors.com
>>> [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of jwcolby
>>> Sent: Thursday, March 05, 2009 12:21 PM
>>> To: Access Developers discussion and problem solving
>>> Subject: Re: [AccessD] Changing Table Names
>>>
>>>
>>>  > I usually use Rick Fishers Find and replace to do that type of
>>> thing..
>>>
>>> I also use this tool.
>>>
>>> OTOH turning on the property in the database mostly kinda sorta works.
>>>
>>> Options / General / Name autocorrect.
>>>
>>> OTOH it might also corrupt your database, slow things down, allow
>>> users to change things unintentionally etc.
>>>
>>> John W. Colby
>>> www.ColbyConsulting.com
>> --
>> 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
>>
>