Tom Wickerath said:Hi Zev,
I see this problem on a frequent basis. The only way I have been able to
get
a setting of [None] to stick, is to create a brand new database and then
import all objects into it. Here is my standard blurb on doing this:
Create a brand new database and immediately disable the NameAutocorrupt
feature (see: http://allenbrowne.com/bug-03.html for reasons why you want
to
do this). Then import all objects from the suspect database into the new
database, one group at a time. In other words, import all tables (but not
linked tables), then import all queries, then all forms, etc. While Access
will allow you to import all objects in one operation, the experts at FMS,
Inc. (a Microsoft Partner), have stated that it is best to import objects
one
group at a time (Reference:
http://www.fmsinc.com/ubb/Forum12/HTML/000285.html).
Recreate any linked tables from scratch. Access can cache a lot of
information about linked tables, which may no longer be valid, so it's
always
best to recreate the linked tables from scratch. When importing local
tables,
make sure to check the option to import relationships, menus and toolbars,
and import/export specs. If any of the local tables in the source DB are
hidden, you'll need to first unhide them. You will need to set the checked
references to match the source database, along with any startup options
set
under Tools > Startup. Going through this process often times solves
corruption problems, because you get a new set of the hidden system tables
(the tables whose names start with "MSYS"). These system tables are
updated
appropriately as you import objects.
This may sound like a lot of work, but it really isn't. Creating a new
container DB, disabling NameAutocorrect, importing all objects one group
at a
time, re-establishing any linked tables, setting startup options, and
setting
references to match the source DB is usually a fairly quick procedure.
When
you are in the Visual Basic Editor, in order to check that the references
match the source DB, you should do a Debug > Compile ProjectName as well.
Tom Wickerath
Microsoft Access MVP
http://www.access.qbuilt.com/html/expert_contributors.html
http://www.access.qbuilt.com/html/search.html
__________________________________________
Zev said:I am runing in Access 2003 I am seting the table datasheet name to none
when
I come back to the table its falls back to Auto Y dose it fall back to
Auto
when I just changed it to None?
Thak You
Zev
Zev said:I am runing in Access 2003 I am seting the table datasheet name to
none when
I come back to the table its falls back to Auto Y dose it fall back
to Auto
when I just changed it to None?
Thak You
Zev
RoyVidar said:Zev said:I am runing in Access 2003 I am seting the table datasheet name to
none when
I come back to the table its falls back to Auto Y dose it fall back
to Auto
when I just changed it to None?
Thak You
Zev
I think that in the 2000 and 2002 version, it's OK to set this
property in the design view, but in 2003, you need to do it through
code to stick. I e
dim db as dao.database
dim td as dao.tabledef
set db = currentdb
db.tabledefs("mytbl").properties("SubDataSheetName").value = "[none]"
Tom Wickerath said:Hi Gina,
I'm thinking that the issue of a subdatasheet setting of [None] not
sticking, and reverting back to [Auto], is not necessarily related to the
Name Autocorrect setting. I always disable Name Autocorrect from the
git-go,
whereas setting subdatasheets to [None] is something I tend to do later in
the development cycle. The only thing that I can think of is that this
setting not sticking represents some subtle form of corruption. I have
experienced it many many times, and Name Autocorrect is always disabled.
Tom Wickerath
Microsoft Access MVP
http://www.access.qbuilt.com/html/expert_contributors.html
http://www.access.qbuilt.com/html/search.html
__________________________________________
Gina Whipp said:Tom,
I have been successful with...
1. Enter database and disable the Name AutoCorrect
2. Exit the database
3. Re-enter the database and set all my tables to [None]
Gina Whipp
Want to reply to this thread or ask your own question?
You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.