Frequently used databases that I put together while on Windows 95/98/XP
platforms are now causing error messages: "The document cws.mdf caused a
serious error the last time it was opened. Would you like to continue
opening it?" Online info: Office, ID: 10043, Source Office Error Messages,
Version: 11.0. Further info indicates that my data bases are being placed on
a disabled items list.

I have successfully completed Genuine Windows & Office validation. Do I
dare to remove them from disable items list? What is the best way to
approach this problem? TIA JP

Hi.

> Further info indicates that my data bases are being placed on
> a disabled items list.

Press the <SHIFT> key and keep holding it down while opening the database
file, until the database is completely open. Select the Help menu -> About
Microsoft Office Access to open the "About Microsoft Office Access" dialog
window. Select the "Disabled Items..." button in the lower right corner of
the window to open the "Disabled Items" dialog window.

You will see a list of the items that have been disabled because they
prevented Access from functioning properly. Before you enable each item on
the list, you must determine what the problem is (it must be very serious if
Access disabled it automatically), fix it, then re-enable the item. You
will probably have to close, then reopen Access, for the re-enabling to take
effect.

Without knowing what the exact cause is (your listed items may help here),
we can't advise a fix. The type of problems that Access disables on startup
are the ones that cause fatal errors, i.e., crashes.

HTH.
Gunny

See http://www.QBuilt.com for all your database needs.
See http://www.Access.QBuilt.com for Microsoft Access tips and tutorials.
Blogs: www.DataDevilDog.BlogSpot.com, www.DatabaseTips.BlogSpot.com
http://www.Access.QBuilt.com/html/ex...ributors2.html for contact
info.


"justphilip2003" <(E-Mail Removed)> wrote in message
news:AB4A7C97-ADE2-4CE3-AD92-(E-Mail Removed)...
> Frequently used databases that I put together while on Windows 95/98/XP
> platforms are now causing error messages: "The document cws.mdf caused a
> serious error the last time it was opened. Would you like to continue
> opening it?" Online info: Office, ID: 10043, Source Office Error
> Messages,
> Version: 11.0. Further info indicates that my data bases are being placed
> on
> a disabled items list.
>
> I have successfully completed Genuine Windows & Office validation. Do I
> dare to remove them from disable items list? What is the best way to
> approach this problem? TIA JP

Your instructions were helpful for getting into the database for review. I
did so and I exercised ever element (table, querry, form, and report - there
were no pages, macros or modules to test) in the DB with no problems. The
proceedure you gave me apparently clears the DB from the disabled list
because it is cleared. I closed the DB and Access; went back in without
"shift key" resulting in same error messages. Nothing to fix in the DB is
there a safe way to rid Access of this error message? TIA JP

"'69 Camaro" wrote:

> Hi.
>
> > Further info indicates that my data bases are being placed on
> > a disabled items list.
>
> Press the <SHIFT> key and keep holding it down while opening the database
> file, until the database is completely open. Select the Help menu -> About
> Microsoft Office Access to open the "About Microsoft Office Access" dialog
> window. Select the "Disabled Items..." button in the lower right corner of
> the window to open the "Disabled Items" dialog window.
>
> You will see a list of the items that have been disabled because they
> prevented Access from functioning properly. Before you enable each item on
> the list, you must determine what the problem is (it must be very serious if
> Access disabled it automatically), fix it, then re-enable the item. You
> will probably have to close, then reopen Access, for the re-enabling to take
> effect.
>
> Without knowing what the exact cause is (your listed items may help here),
> we can't advise a fix. The type of problems that Access disables on startup
> are the ones that cause fatal errors, i.e., crashes.
>
> HTH.
> Gunny
>
> See http://www.QBuilt.com for all your database needs.
> See http://www.Access.QBuilt.com for Microsoft Access tips and tutorials.
> Blogs: www.DataDevilDog.BlogSpot.com, www.DatabaseTips.BlogSpot.com
> http://www.Access.QBuilt.com/html/ex...ributors2.html for contact
> info.
>
>
> "justphilip2003" <(E-Mail Removed)> wrote in message
> news:AB4A7C97-ADE2-4CE3-AD92-(E-Mail Removed)...
> > Frequently used databases that I put together while on Windows 95/98/XP
> > platforms are now causing error messages: "The document cws.mdf caused a
> > serious error the last time it was opened. Would you like to continue
> > opening it?" Online info: Office, ID: 10043, Source Office Error
> > Messages,
> > Version: 11.0. Further info indicates that my data bases are being placed
> > on
> > a disabled items list.
> >
> > I have successfully completed Genuine Windows & Office validation. Do I
> > dare to remove them from disable items list? What is the best way to
> > approach this problem? TIA JP
>
>
>

Hi.

> I closed the DB and Access; went back in without
> "shift key" resulting in same error messages.

You _must_ fix the item prior to removing if from the disabled list.
Otherwise, the next time you open the database file Access will disable that
item put it back on the disabled list.

> is
> there a safe way to rid Access of this error message?

Since you don't have any code modules or macros, do you have any ActiveX
controls embedded on forms or reports? If so, remove it from Design View,
save the form or report, then add the ActiveX control again and save the
form or report again. Do you have a default printer assigned? Have you
compacted and repaired the database? If so, have you created a new file and
imported all of the objects into it by groups? First the tables, then the
queries, then the forms, et cetera.

To troubleshoot it, I'd normally open the database with the shift key bypass
method, then put a breakpoint in the code in the startup form's Form_Load( )
event (or the Form_Open( ) event, whichever is the first VBA event in your
database) and step through the code until it crashes. I'd fix whatever
causes it to crash and continue stepping through the code to find every
crash point, and then fix the cause of every crash point. When everything
works on each disabled item, I'd re-enable the disabled item, then step
through the code on the next disabled item, and continue on until everything
was fixed and re-enabled. And then I'd create a new database and import the
objects, group by group, from the original database into it.

HTH.
Gunny

See http://www.QBuilt.com for all your database needs.
See http://www.Access.QBuilt.com for Microsoft Access tips and tutorials.
Blogs: www.DataDevilDog.BlogSpot.com, www.DatabaseTips.BlogSpot.com
http://www.Access.QBuilt.com/html/ex...ributors2.html for contact
info.


"justphilip2003" <(E-Mail Removed)> wrote in message
news:742DF337-E190-4995-83CC-(E-Mail Removed)...
> Your instructions were helpful for getting into the database for review.
> I
> did so and I exercised ever element (table, querry, form, and report -
> there
> were no pages, macros or modules to test) in the DB with no problems. The
> proceedure you gave me apparently clears the DB from the disabled list
> because it is cleared. I closed the DB and Access; went back in without
> "shift key" resulting in same error messages. Nothing to fix in the DB is
> there a safe way to rid Access of this error message? TIA JP
>
> "'69 Camaro" wrote:
>
>> Hi.
>>
>> > Further info indicates that my data bases are being placed on
>> > a disabled items list.
>>
>> Press the <SHIFT> key and keep holding it down while opening the database
>> file, until the database is completely open. Select the Help menu ->
>> About
>> Microsoft Office Access to open the "About Microsoft Office Access"
>> dialog
>> window. Select the "Disabled Items..." button in the lower right corner
>> of
>> the window to open the "Disabled Items" dialog window.
>>
>> You will see a list of the items that have been disabled because they
>> prevented Access from functioning properly. Before you enable each item
>> on
>> the list, you must determine what the problem is (it must be very serious
>> if
>> Access disabled it automatically), fix it, then re-enable the item. You
>> will probably have to close, then reopen Access, for the re-enabling to
>> take
>> effect.
>>
>> Without knowing what the exact cause is (your listed items may help
>> here),
>> we can't advise a fix. The type of problems that Access disables on
>> startup
>> are the ones that cause fatal errors, i.e., crashes.
>>
>> HTH.
>> Gunny
>>
>> See http://www.QBuilt.com for all your database needs.
>> See http://www.Access.QBuilt.com for Microsoft Access tips and tutorials.
>> Blogs: www.DataDevilDog.BlogSpot.com, www.DatabaseTips.BlogSpot.com
>> http://www.Access.QBuilt.com/html/ex...ributors2.html for contact
>> info.
>>
>>
>> "justphilip2003" <(E-Mail Removed)> wrote in
>> message
>> news:AB4A7C97-ADE2-4CE3-AD92-(E-Mail Removed)...
>> > Frequently used databases that I put together while on Windows 95/98/XP
>> > platforms are now causing error messages: "The document cws.mdf caused
>> > a
>> > serious error the last time it was opened. Would you like to continue
>> > opening it?" Online info: Office, ID: 10043, Source Office Error
>> > Messages,
>> > Version: 11.0. Further info indicates that my data bases are being
>> > placed
>> > on
>> > a disabled items list.
>> >
>> > I have successfully completed Genuine Windows & Office validation. Do
>> > I
>> > dare to remove them from disable items list? What is the best way to
>> > approach this problem? TIA JP
>>
>>
>>

Hi Gunny'
I am still getting "This file may not be safe..." message even though there
no longer are any disabled files. I do not know about using ActiveX (unless
=Now() or =Page are ActiveX). Here is what I did: (1) I assumed there are no
ActiveX coding in db, (2) One table had been altered and AutoNumbers were
deleted - I put them back in with coding indicating deleted records, reviewed
all queries, reports and forms fixing all visible data and coding problems,
(3) created a new data base name and imported individual segments as
instructed. It was fun, I learn a lot! Is the unsafe mwssage just Vista
security not being properly tuned or do I still have a problem? TIA JP

"'69 Camaro" wrote:

> Hi.
>
> > I closed the DB and Access; went back in without
> > "shift key" resulting in same error messages.
>
> You _must_ fix the item prior to removing if from the disabled list.
> Otherwise, the next time you open the database file Access will disable that
> item put it back on the disabled list.
>
> > is
> > there a safe way to rid Access of this error message?
>
> Since you don't have any code modules or macros, do you have any ActiveX
> controls embedded on forms or reports? If so, remove it from Design View,
> save the form or report, then add the ActiveX control again and save the
> form or report again. Do you have a default printer assigned? Have you
> compacted and repaired the database? If so, have you created a new file and
> imported all of the objects into it by groups? First the tables, then the
> queries, then the forms, et cetera.
>
> To troubleshoot it, I'd normally open the database with the shift key bypass
> method, then put a breakpoint in the code in the startup form's Form_Load( )
> event (or the Form_Open( ) event, whichever is the first VBA event in your
> database) and step through the code until it crashes. I'd fix whatever
> causes it to crash and continue stepping through the code to find every
> crash point, and then fix the cause of every crash point. When everything
> works on each disabled item, I'd re-enable the disabled item, then step
> through the code on the next disabled item, and continue on until everything
> was fixed and re-enabled. And then I'd create a new database and import the
> objects, group by group, from the original database into it.
>
> HTH.
> Gunny
>
> See http://www.QBuilt.com for all your database needs.
> See http://www.Access.QBuilt.com for Microsoft Access tips and tutorials.
> Blogs: www.DataDevilDog.BlogSpot.com, www.DatabaseTips.BlogSpot.com
> http://www.Access.QBuilt.com/html/ex...ributors2.html for contact
> info.
>
>
> "justphilip2003" <(E-Mail Removed)> wrote in message
> news:742DF337-E190-4995-83CC-(E-Mail Removed)...
> > Your instructions were helpful for getting into the database for review.
> > I
> > did so and I exercised ever element (table, querry, form, and report -
> > there
> > were no pages, macros or modules to test) in the DB with no problems. The
> > proceedure you gave me apparently clears the DB from the disabled list
> > because it is cleared. I closed the DB and Access; went back in without
> > "shift key" resulting in same error messages. Nothing to fix in the DB is
> > there a safe way to rid Access of this error message? TIA JP
> >
> > "'69 Camaro" wrote:
> >
> >> Hi.
> >>
> >> > Further info indicates that my data bases are being placed on
> >> > a disabled items list.
> >>
> >> Press the <SHIFT> key and keep holding it down while opening the database
> >> file, until the database is completely open. Select the Help menu ->
> >> About
> >> Microsoft Office Access to open the "About Microsoft Office Access"
> >> dialog
> >> window. Select the "Disabled Items..." button in the lower right corner
> >> of
> >> the window to open the "Disabled Items" dialog window.
> >>
> >> You will see a list of the items that have been disabled because they
> >> prevented Access from functioning properly. Before you enable each item
> >> on
> >> the list, you must determine what the problem is (it must be very serious
> >> if
> >> Access disabled it automatically), fix it, then re-enable the item. You
> >> will probably have to close, then reopen Access, for the re-enabling to
> >> take
> >> effect.
> >>
> >> Without knowing what the exact cause is (your listed items may help
> >> here),
> >> we can't advise a fix. The type of problems that Access disables on
> >> startup
> >> are the ones that cause fatal errors, i.e., crashes.
> >>
> >> HTH.
> >> Gunny
> >>
> >> See http://www.QBuilt.com for all your database needs.
> >> See http://www.Access.QBuilt.com for Microsoft Access tips and tutorials.
> >> Blogs: www.DataDevilDog.BlogSpot.com, www.DatabaseTips.BlogSpot.com
> >> http://www.Access.QBuilt.com/html/ex...ributors2.html for contact
> >> info.
> >>
> >>
> >> "justphilip2003" <(E-Mail Removed)> wrote in
> >> message
> >> news:AB4A7C97-ADE2-4CE3-AD92-(E-Mail Removed)...
> >> > Frequently used databases that I put together while on Windows 95/98/XP
> >> > platforms are now causing error messages: "The document cws.mdf caused
> >> > a
> >> > serious error the last time it was opened. Would you like to continue
> >> > opening it?" Online info: Office, ID: 10043, Source Office Error
> >> > Messages,
> >> > Version: 11.0. Further info indicates that my data bases are being
> >> > placed
> >> > on
> >> > a disabled items list.
> >> >
> >> > I have successfully completed Genuine Windows & Office validation. Do
> >> > I
> >> > dare to remove them from disable items list? What is the best way to
> >> > approach this problem? TIA JP
> >>
> >>
> >>
>
>
>

I sloved my problem by lowering Access' macro security to low.
(Access/Tools/Macro/Security ==> low). Also said yes for all user to be
warned on future macros incursions. The fact that every Database on my PC
including MS examples were incurring the Unsafe message lead me to thisfix.
Thanks for uour help. JP

"justphilip2003" wrote:

> Hi Gunny'
> I am still getting "This file may not be safe..." message even though there
> no longer are any disabled files. I do not know about using ActiveX (unless
> =Now() or =Page are ActiveX). Here is what I did: (1) I assumed there are no
> ActiveX coding in db, (2) One table had been altered and AutoNumbers were
> deleted - I put them back in with coding indicating deleted records, reviewed
> all queries, reports and forms fixing all visible data and coding problems,
> (3) created a new data base name and imported individual segments as
> instructed. It was fun, I learn a lot! Is the unsafe mwssage just Vista
> security not being properly tuned or do I still have a problem? TIA JP
>
> "'69 Camaro" wrote:
>
> > Hi.
> >
> > > I closed the DB and Access; went back in without
> > > "shift key" resulting in same error messages.
> >
> > You _must_ fix the item prior to removing if from the disabled list.
> > Otherwise, the next time you open the database file Access will disable that
> > item put it back on the disabled list.
> >
> > > is
> > > there a safe way to rid Access of this error message?
> >
> > Since you don't have any code modules or macros, do you have any ActiveX
> > controls embedded on forms or reports? If so, remove it from Design View,
> > save the form or report, then add the ActiveX control again and save the
> > form or report again. Do you have a default printer assigned? Have you
> > compacted and repaired the database? If so, have you created a new file and
> > imported all of the objects into it by groups? First the tables, then the
> > queries, then the forms, et cetera.
> >
> > To troubleshoot it, I'd normally open the database with the shift key bypass
> > method, then put a breakpoint in the code in the startup form's Form_Load( )
> > event (or the Form_Open( ) event, whichever is the first VBA event in your
> > database) and step through the code until it crashes. I'd fix whatever
> > causes it to crash and continue stepping through the code to find every
> > crash point, and then fix the cause of every crash point. When everything
> > works on each disabled item, I'd re-enable the disabled item, then step
> > through the code on the next disabled item, and continue on until everything
> > was fixed and re-enabled. And then I'd create a new database and import the
> > objects, group by group, from the original database into it.
> >
> > HTH.
> > Gunny
> >
> > See http://www.QBuilt.com for all your database needs.
> > See http://www.Access.QBuilt.com for Microsoft Access tips and tutorials.
> > Blogs: www.DataDevilDog.BlogSpot.com, www.DatabaseTips.BlogSpot.com
> > http://www.Access.QBuilt.com/html/ex...ributors2.html for contact
> > info.
> >
> >
> > "justphilip2003" <(E-Mail Removed)> wrote in message
> > news:742DF337-E190-4995-83CC-(E-Mail Removed)...
> > > Your instructions were helpful for getting into the database for review.
> > > I
> > > did so and I exercised ever element (table, querry, form, and report -
> > > there
> > > were no pages, macros or modules to test) in the DB with no problems. The
> > > proceedure you gave me apparently clears the DB from the disabled list
> > > because it is cleared. I closed the DB and Access; went back in without
> > > "shift key" resulting in same error messages. Nothing to fix in the DB is
> > > there a safe way to rid Access of this error message? TIA JP
> > >
> > > "'69 Camaro" wrote:
> > >
> > >> Hi.
> > >>
> > >> > Further info indicates that my data bases are being placed on
> > >> > a disabled items list.
> > >>
> > >> Press the <SHIFT> key and keep holding it down while opening the database
> > >> file, until the database is completely open. Select the Help menu ->
> > >> About
> > >> Microsoft Office Access to open the "About Microsoft Office Access"
> > >> dialog
> > >> window. Select the "Disabled Items..." button in the lower right corner
> > >> of
> > >> the window to open the "Disabled Items" dialog window.
> > >>
> > >> You will see a list of the items that have been disabled because they
> > >> prevented Access from functioning properly. Before you enable each item
> > >> on
> > >> the list, you must determine what the problem is (it must be very serious
> > >> if
> > >> Access disabled it automatically), fix it, then re-enable the item. You
> > >> will probably have to close, then reopen Access, for the re-enabling to
> > >> take
> > >> effect.
> > >>
> > >> Without knowing what the exact cause is (your listed items may help
> > >> here),
> > >> we can't advise a fix. The type of problems that Access disables on
> > >> startup
> > >> are the ones that cause fatal errors, i.e., crashes.
> > >>
> > >> HTH.
> > >> Gunny
> > >>
> > >> See http://www.QBuilt.com for all your database needs.
> > >> See http://www.Access.QBuilt.com for Microsoft Access tips and tutorials.
> > >> Blogs: www.DataDevilDog.BlogSpot.com, www.DatabaseTips.BlogSpot.com
> > >> http://www.Access.QBuilt.com/html/ex...ributors2.html for contact
> > >> info.
> > >>
> > >>
> > >> "justphilip2003" <(E-Mail Removed)> wrote in
> > >> message
> > >> news:AB4A7C97-ADE2-4CE3-AD92-(E-Mail Removed)...
> > >> > Frequently used databases that I put together while on Windows 95/98/XP
> > >> > platforms are now causing error messages: "The document cws.mdf caused
> > >> > a
> > >> > serious error the last time it was opened. Would you like to continue
> > >> > opening it?" Online info: Office, ID: 10043, Source Office Error
> > >> > Messages,
> > >> > Version: 11.0. Further info indicates that my data bases are being
> > >> > placed
> > >> > on
> > >> > a disabled items list.
> > >> >
> > >> > I have successfully completed Genuine Windows & Office validation. Do
> > >> > I
> > >> > dare to remove them from disable items list? What is the best way to
> > >> > approach this problem? TIA JP
> > >>
> > >>
> > >>
> >
> >
> >

Hi.

> Is the unsafe mwssage just Vista
> security not being properly tuned or do I still have a problem?

No. That's the default macro security message from Access 2003. I see that
you already determined how to avoid that by setting the macro security to
low. Good job!

> Also said yes for all user to be
> warned on future macros incursions.

You may want to change that setting later to avoid getting warned for every
Access database that has VBA code in it, or uses unsafe expressions in form
or report properties, or uses action queries.

HTH.
Gunny

See http://www.QBuilt.com for all your database needs.
See http://www.Access.QBuilt.com for Microsoft Access tips and tutorials.
Blogs: www.DataDevilDog.BlogSpot.com, www.DatabaseTips.BlogSpot.com
http://www.Access.QBuilt.com/html/ex...ributors2.html for contact
info.


"justphilip2003" <(E-Mail Removed)> wrote in message
news:C335563B-EC23-46D8-869A-(E-Mail Removed)...
>I sloved my problem by lowering Access' macro security to low.
> (Access/Tools/Macro/Security ==> low). Also said yes for all user to be
> warned on future macros incursions. The fact that every Database on my PC
> including MS examples were incurring the Unsafe message lead me to
> thisfix.
> Thanks for uour help. JP
>
> "justphilip2003" wrote:
>
>> Hi Gunny'
>> I am still getting "This file may not be safe..." message even though
>> there
>> no longer are any disabled files. I do not know about using ActiveX
>> (unless
>> =Now() or =Page are ActiveX). Here is what I did: (1) I assumed there
>> are no
>> ActiveX coding in db, (2) One table had been altered and AutoNumbers were
>> deleted - I put them back in with coding indicating deleted records,
>> reviewed
>> all queries, reports and forms fixing all visible data and coding
>> problems,
>> (3) created a new data base name and imported individual segments as
>> instructed. It was fun, I learn a lot! Is the unsafe mwssage just Vista
>> security not being properly tuned or do I still have a problem? TIA JP
>>
>> "'69 Camaro" wrote:
>>
>> > Hi.
>> >
>> > > I closed the DB and Access; went back in without
>> > > "shift key" resulting in same error messages.
>> >
>> > You _must_ fix the item prior to removing if from the disabled list.
>> > Otherwise, the next time you open the database file Access will disable
>> > that
>> > item put it back on the disabled list.
>> >
>> > > is
>> > > there a safe way to rid Access of this error message?
>> >
>> > Since you don't have any code modules or macros, do you have any
>> > ActiveX
>> > controls embedded on forms or reports? If so, remove it from Design
>> > View,
>> > save the form or report, then add the ActiveX control again and save
>> > the
>> > form or report again. Do you have a default printer assigned? Have
>> > you
>> > compacted and repaired the database? If so, have you created a new
>> > file and
>> > imported all of the objects into it by groups? First the tables, then
>> > the
>> > queries, then the forms, et cetera.
>> >
>> > To troubleshoot it, I'd normally open the database with the shift key
>> > bypass
>> > method, then put a breakpoint in the code in the startup form's
>> > Form_Load( )
>> > event (or the Form_Open( ) event, whichever is the first VBA event in
>> > your
>> > database) and step through the code until it crashes. I'd fix whatever
>> > causes it to crash and continue stepping through the code to find every
>> > crash point, and then fix the cause of every crash point. When
>> > everything
>> > works on each disabled item, I'd re-enable the disabled item, then step
>> > through the code on the next disabled item, and continue on until
>> > everything
>> > was fixed and re-enabled. And then I'd create a new database and
>> > import the
>> > objects, group by group, from the original database into it.
>> >
>> > HTH.
>> > Gunny
>> >
>> > See http://www.QBuilt.com for all your database needs.
>> > See http://www.Access.QBuilt.com for Microsoft Access tips and
>> > tutorials.
>> > Blogs: www.DataDevilDog.BlogSpot.com, www.DatabaseTips.BlogSpot.com
>> > http://www.Access.QBuilt.com/html/ex...ributors2.html for contact
>> > info.
>> >
>> >
>> > "justphilip2003" <(E-Mail Removed)> wrote in
>> > message
>> > news:742DF337-E190-4995-83CC-(E-Mail Removed)...
>> > > Your instructions were helpful for getting into the database for
>> > > review.
>> > > I
>> > > did so and I exercised ever element (table, querry, form, and
>> > > report -
>> > > there
>> > > were no pages, macros or modules to test) in the DB with no problems.
>> > > The
>> > > proceedure you gave me apparently clears the DB from the disabled
>> > > list
>> > > because it is cleared. I closed the DB and Access; went back in
>> > > without
>> > > "shift key" resulting in same error messages. Nothing to fix in the
>> > > DB is
>> > > there a safe way to rid Access of this error message? TIA JP
>> > >
>> > > "'69 Camaro" wrote:
>> > >
>> > >> Hi.
>> > >>
>> > >> > Further info indicates that my data bases are being placed on
>> > >> > a disabled items list.
>> > >>
>> > >> Press the <SHIFT> key and keep holding it down while opening the
>> > >> database
>> > >> file, until the database is completely open. Select the Help
>> > >> menu ->
>> > >> About
>> > >> Microsoft Office Access to open the "About Microsoft Office Access"
>> > >> dialog
>> > >> window. Select the "Disabled Items..." button in the lower right
>> > >> corner
>> > >> of
>> > >> the window to open the "Disabled Items" dialog window.
>> > >>
>> > >> You will see a list of the items that have been disabled because
>> > >> they
>> > >> prevented Access from functioning properly. Before you enable each
>> > >> item
>> > >> on
>> > >> the list, you must determine what the problem is (it must be very
>> > >> serious
>> > >> if
>> > >> Access disabled it automatically), fix it, then re-enable the item.
>> > >> You
>> > >> will probably have to close, then reopen Access, for the re-enabling
>> > >> to
>> > >> take
>> > >> effect.
>> > >>
>> > >> Without knowing what the exact cause is (your listed items may help
>> > >> here),
>> > >> we can't advise a fix. The type of problems that Access disables on
>> > >> startup
>> > >> are the ones that cause fatal errors, i.e., crashes.
>> > >>
>> > >> HTH.
>> > >> Gunny
>> > >>
>> > >> See http://www.QBuilt.com for all your database needs.
>> > >> See http://www.Access.QBuilt.com for Microsoft Access tips and
>> > >> tutorials.
>> > >> Blogs: www.DataDevilDog.BlogSpot.com, www.DatabaseTips.BlogSpot.com
>> > >> http://www.Access.QBuilt.com/html/ex...ributors2.html for
>> > >> contact
>> > >> info.
>> > >>
>> > >>
>> > >> "justphilip2003" <(E-Mail Removed)> wrote in
>> > >> message
>> > >> news:AB4A7C97-ADE2-4CE3-AD92-(E-Mail Removed)...
>> > >> > Frequently used databases that I put together while on Windows
>> > >> > 95/98/XP
>> > >> > platforms are now causing error messages: "The document cws.mdf
>> > >> > caused
>> > >> > a
>> > >> > serious error the last time it was opened. Would you like to
>> > >> > continue
>> > >> > opening it?" Online info: Office, ID: 10043, Source Office Error
>> > >> > Messages,
>> > >> > Version: 11.0. Further info indicates that my data bases are
>> > >> > being
>> > >> > placed
>> > >> > on
>> > >> > a disabled items list.
>> > >> >
>> > >> > I have successfully completed Genuine Windows & Office validation.
>> > >> > Do
>> > >> > I
>> > >> > dare to remove them from disable items list? What is the best way
>> > >> > to
>> > >> > approach this problem? TIA JP
>> > >>
>> > >>
>> > >>
>> >
>> >
>> >