Table called "Name AutoCorrect Save Failures"

[BobC]

I inherited a 2007 Access application that has a MACRO related to a
Table called "Name AutoCorrect Save Failures" that I have no idea what
it is? I had deleted it, and it cause me not to be able to create a
ACCDE file!
Any clues?

[ruralguy via AccessMonster.com]

Forgot the link I had.
http://www.btabdevelopment.com/main/QuickTutorials/A2K7HowtoDisableNameAutoCorrect/tabid/137/Default.aspx

ruralguy wrote:
>Have you turned off Name AutoCorrect?
>Did you delete the table or the Macro or both?
>You did that on a back up right?

--
RuralGuy (RG for short) aka Allan Bunch MS Access MVP - acXP WinXP Pro
Please post back to this forum so all may benefit.

Message posted via AccessMonster.com
http://www.accessmonster.com/Uwe/Forums.aspx/access-forms/200912/1

[ruralguy via AccessMonster.com]

Have you turned off Name AutoCorrect?
Did you delete the table or the Macro or both?
You did that on a back up right?

--

[BobC]

I DID NOT turn off AutoCorrect ... wherever that is????? ... I will look?
I deleted only the table ... Whick is likely why I had the problem in
the first place.
I do not know where the macro is?
This is not a back up... this is in the actual live database.

[BobC]

THANK YOU!
I assume this what I have heard called "autoCorrupt"?

[Larry Linson]

I'm reasonably sure his point was that before you go messing with a
database, it's A Really Good Idea that you make a backup, just in case, for
example, something you do makes it where it doesn't work (and, unlike this
situation, you can't ever get it to work again).

It's also not a good idea, in fact A Really Bad Idea, to just delete from a
database anything unless you KNOW what it was supposed to do, and why it is
no longer needed.

It's A Good Idea to split your database into a front end (queries, forms,
reports, macros, and modules) and a separate back end (tables, the data in
the tables, and relationships) and link the front end to the back end using
the Linked Table Manager. That way, even if you manage to make an
irrecoverable mess of the front end (user interface), you have not lost all
the business data in the backend.

Larry Linson
Microsoft Office Access MVP

"BobC" <Bob.Call...@cox.net> wrote in message
news:KcVTm.17828$_b5....@newsfe22.iad...

[john ridge]

Larry

Totally agree with your advice.

The following link http://msdn.microsoft.com/en-us/library/aa...office.10).aspx also gives some really useful insights for others into how Name AutoCorrect works and why it cannot be expected to work in certain essentially user limiting scenarios.

I would additionally note that "Track Name AutoCorrect Info" stores the name change information in table ="Name AutoCorrect Log" and that this table is made visible using tools>options>view>system objects

> On Tuesday, December 08, 2009 11:43 PM BobC wrote:

> I inherited a 2007 Access application that has a MACRO related to a
> Table called "Name AutoCorrect Save Failures" that I have no idea what
> it is? I had deleted it, and it cause me not to be able to create a
> ACCDE file!
> Any clues?

>> On Wednesday, December 09, 2009 9:15 AM ruralguy via AccessMonster.com wrote:

>> Have you turned off Name AutoCorrect?
>> Did you delete the table or the Macro or both?
>> You did that on a back up right?
>>
>> BobC wrote:
>>

>> --
>> RuralGuy (RG for short) aka Allan Bunch MS Access MVP - acXP WinXP Pro
>> Please post back to this forum so all may benefit.
>>
>> Message posted via AccessMonster.com
>> http://www.accessmonster.com/Uwe/Forums.aspx/access-forms/200912/1

>>> On Wednesday, December 09, 2009 9:17 AM ruralguy via AccessMonster.com wrote:

>>> Forgot the link I had.
>>> http://www.btabdevelopment.com/main/QuickTutorials/A2K7HowtoDisableNameAutoCorrect/tabid/137/Default.aspx
>>>
>>>
>>>
>>> ruralguy wrote:
>>>

>>> --
>>> RuralGuy (RG for short) aka Allan Bunch MS Access MVP - acXP WinXP Pro
>>> Please post back to this forum so all may benefit.
>>>
>>> Message posted via AccessMonster.com
>>> http://www.accessmonster.com/Uwe/Forums.aspx/access-forms/200912/1

>>>> On Wednesday, December 09, 2009 5:07 PM BobC wrote:

>>>> I DID NOT turn off AutoCorrect ... wherever that is????? ... I will look?
>>>> I deleted only the table ... Whick is likely why I had the problem in
>>>> the first place.
>>>> I do not know where the macro is?
>>>> This is not a back up... this is in the actual live database.
>>>>
>>>>
>>>> ruralguy via AccessMonster.com wrote:

>>>>> On Wednesday, December 09, 2009 5:10 PM BobC wrote:

>>>>> THANK YOU!
>>>>> I assume this what I have heard called "autoCorrupt"?
>>>>>
>>>>> ruralguy via AccessMonster.com wrote:

>>>>>> On Thursday, December 10, 2009 1:26 AM Larry Linson wrote:

>>>>>> I am reasonably sure his point was that before you go messing with a
>>>>>> database, it is A Really Good Idea that you make a backup, just in case, for
>>>>>> example, something you do makes it where it does not work (and, unlike this
>>>>>> situation, you cannot ever get it to work again).
>>>>>>
>>>>>> it is also not a good idea, in fact A Really Bad Idea, to just delete from a

>>>>>> database anything unless you KNOW what it was supposed to do, and why it is
>>>>>> no longer needed.
>>>>>>

>>>>>> it is A Good Idea to split your database into a front end (queries, forms,

>>>>>> reports, macros, and modules) and a separate back end (tables, the data in
>>>>>> the tables, and relationships) and link the front end to the back end using
>>>>>> the Linked Table Manager. That way, even if you manage to make an
>>>>>> irrecoverable mess of the front end (user interface), you have not lost all
>>>>>> the business data in the backend.
>>>>>>
>>>>>> Larry Linson
>>>>>> Microsoft Office Access MVP

>>>>>> Submitted via EggHeadCafe - Software Developer Portal of Choice
>>>>>> Flat file Database with LINQ and ASP.NET jQuery Page Methods
>>>>>> http://www.eggheadcafe.com/tutorials/aspnet/c8c43191-c3a3-4c61-801a-2433a701f4f6/flat-file-database-with-linq-and-aspnet-jquery-page-methods.aspx