I have an MDB that was developed in Access 2003 and now running in Access
2007. It has not been converted to an ACCDB file format yet. The file is
around 30MB with over 40,000 records that are used daily by approximately
200 users across a network. It is not split into a back-end or front-end.
It is on a share network drive that everyone accesses. I cannot, for
several reasons, split it and put a front-end on all the users desktop
across the business.

The problem I am having since upgrading to Office 2007 is that for no
apparent reason, all the visual basic code vanishes. All the forms,
reports, queries and tables seem to be fine, but the code is missing. We
are running Office 2007 SP1 on all the computers. The database starts fine,
the main menu appears, but nothing can be done afterwards.

I first thought that nightly backups were corrupting it, but the start time
of those were moved to a later time just to see if it made a difference. I
put in a time-out procedure that if there is no activity at the user level
after 30 minutes, the database closes for that user. I was thinking that
maybe someone was rebooting the computer while a database was open.

Another thought was that there were network issues across the share drives,
but the network groups says that there is no indication of any problems.

I did not have this issue on Office 2003 and never once had to do a restore.
Now, on Office 2007, I am restoring the entire database and copying tables
at least once a week. We are planing on converting the database to the new
Access 2007 on May 11th to see if that helps.

Any ideas or suggestions would be very helpful. I am at a complete loss on
this one. Thanks.

It is all attributable to Access 2007's enhanced(?) security features.
It''s default behavior is to shut off all VBA code and Macros.
Google these groups for "Trusted Locations", "Access 2007 security
features", etc.
There are solutions. Changing to ACCDB will not fix it.

Regards

Kevin

"Chuck" <Chuck NY 1958 @Yahoo.com> wrote in message
news:%23I$p%(E-Mail Removed)...
>I have an MDB that was developed in Access 2003 and now running in Access
>2007. It has not been converted to an ACCDB file format yet. The file is
>around 30MB with over 40,000 records that are used daily by approximately
>200 users across a network. It is not split into a back-end or front-end.
>It is on a share network drive that everyone accesses. I cannot, for
>several reasons, split it and put a front-end on all the users desktop
>across the business.
>
> The problem I am having since upgrading to Office 2007 is that for no
> apparent reason, all the visual basic code vanishes. All the forms,
> reports, queries and tables seem to be fine, but the code is missing. We
> are running Office 2007 SP1 on all the computers. The database starts
> fine, the main menu appears, but nothing can be done afterwards.
>
> I first thought that nightly backups were corrupting it, but the start
> time of those were moved to a later time just to see if it made a
> difference. I put in a time-out procedure that if there is no activity at
> the user level after 30 minutes, the database closes for that user. I was
> thinking that maybe someone was rebooting the computer while a database
> was open.
>
> Another thought was that there were network issues across the share
> drives, but the network groups says that there is no indication of any
> problems.
>
> I did not have this issue on Office 2003 and never once had to do a
> restore. Now, on Office 2007, I am restoring the entire database and
> copying tables at least once a week. We are planing on converting the
> database to the new Access 2007 on May 11th to see if that helps.
>
> Any ideas or suggestions would be very helpful. I am at a complete loss
> on this one. Thanks.

It is all attributable to Access 2007's enhanced(?) security features.
It''s default behavior is to shut off all VBA code and Macros.
Google these groups for "Trusted Locations", "Access 2007 security
features", etc.
There are solutions. Changing to ACCDB will not fix it.

Regards

Kevin

"Chuck" <Chuck NY 1958 @Yahoo.com> wrote in message
news:%23I$p%(E-Mail Removed)...
>I have an MDB that was developed in Access 2003 and now running in Access
>2007. It has not been converted to an ACCDB file format yet. The file is
>around 30MB with over 40,000 records that are used daily by approximately
>200 users across a network. It is not split into a back-end or front-end.
>It is on a share network drive that everyone accesses. I cannot, for
>several reasons, split it and put a front-end on all the users desktop
>across the business.
>
> The problem I am having since upgrading to Office 2007 is that for no
> apparent reason, all the visual basic code vanishes. All the forms,
> reports, queries and tables seem to be fine, but the code is missing. We
> are running Office 2007 SP1 on all the computers. The database starts
> fine, the main menu appears, but nothing can be done afterwards.
>
> I first thought that nightly backups were corrupting it, but the start
> time of those were moved to a later time just to see if it made a
> difference. I put in a time-out procedure that if there is no activity at
> the user level after 30 minutes, the database closes for that user. I was
> thinking that maybe someone was rebooting the computer while a database
> was open.
>
> Another thought was that there were network issues across the share
> drives, but the network groups says that there is no indication of any
> problems.
>
> I did not have this issue on Office 2003 and never once had to do a
> restore. Now, on Office 2007, I am restoring the entire database and
> copying tables at least once a week. We are planing on converting the
> database to the new Access 2007 on May 11th to see if that helps.
>
> Any ideas or suggestions would be very helpful. I am at a complete loss
> on this one. Thanks.

I know about the security features. It does prompt the user to enable the
code and macros. It works when the user enables the code, but would it
actually delete or disable it for all users if the person selects the wrong
choice?


"KC-Mass" <connearney_AT_comcast_Period_net> wrote in message
news:(E-Mail Removed)...
> It is all attributable to Access 2007's enhanced(?) security features.
> It''s default behavior is to shut off all VBA code and Macros.
> Google these groups for "Trusted Locations", "Access 2007 security
> features", etc.
> There are solutions. Changing to ACCDB will not fix it.
>
> Regards
>
> Kevin
>
> "Chuck" <Chuck NY 1958 @Yahoo.com> wrote in message
> news:%23I$p%(E-Mail Removed)...
>>I have an MDB that was developed in Access 2003 and now running in Access
>>2007. It has not been converted to an ACCDB file format yet. The file is
>>around 30MB with over 40,000 records that are used daily by approximately
>>200 users across a network. It is not split into a back-end or front-end.
>>It is on a share network drive that everyone accesses. I cannot, for
>>several reasons, split it and put a front-end on all the users desktop
>>across the business.
>>
>> The problem I am having since upgrading to Office 2007 is that for no
>> apparent reason, all the visual basic code vanishes. All the forms,
>> reports, queries and tables seem to be fine, but the code is missing. We
>> are running Office 2007 SP1 on all the computers. The database starts
>> fine, the main menu appears, but nothing can be done afterwards.
>>
>> I first thought that nightly backups were corrupting it, but the start
>> time of those were moved to a later time just to see if it made a
>> difference. I put in a time-out procedure that if there is no activity
>> at the user level after 30 minutes, the database closes for that user. I
>> was thinking that maybe someone was rebooting the computer while a
>> database was open.
>>
>> Another thought was that there were network issues across the share
>> drives, but the network groups says that there is no indication of any
>> problems.
>>
>> I did not have this issue on Office 2003 and never once had to do a
>> restore. Now, on Office 2007, I am restoring the entire database and
>> copying tables at least once a week. We are planing on converting the
>> database to the new Access 2007 on May 11th to see if that helps.
>>
>> Any ideas or suggestions would be very helpful. I am at a complete loss
>> on this one. Thanks.
>
>

I know about the security features. It does prompt the user to enable the
code and macros. It works when the user enables the code, but would it
actually delete or disable it for all users if the person selects the wrong
choice?


"KC-Mass" <connearney_AT_comcast_Period_net> wrote in message
news:(E-Mail Removed)...
> It is all attributable to Access 2007's enhanced(?) security features.
> It''s default behavior is to shut off all VBA code and Macros.
> Google these groups for "Trusted Locations", "Access 2007 security
> features", etc.
> There are solutions. Changing to ACCDB will not fix it.
>
> Regards
>
> Kevin
>
> "Chuck" <Chuck NY 1958 @Yahoo.com> wrote in message
> news:%23I$p%(E-Mail Removed)...
>>I have an MDB that was developed in Access 2003 and now running in Access
>>2007. It has not been converted to an ACCDB file format yet. The file is
>>around 30MB with over 40,000 records that are used daily by approximately
>>200 users across a network. It is not split into a back-end or front-end.
>>It is on a share network drive that everyone accesses. I cannot, for
>>several reasons, split it and put a front-end on all the users desktop
>>across the business.
>>
>> The problem I am having since upgrading to Office 2007 is that for no
>> apparent reason, all the visual basic code vanishes. All the forms,
>> reports, queries and tables seem to be fine, but the code is missing. We
>> are running Office 2007 SP1 on all the computers. The database starts
>> fine, the main menu appears, but nothing can be done afterwards.
>>
>> I first thought that nightly backups were corrupting it, but the start
>> time of those were moved to a later time just to see if it made a
>> difference. I put in a time-out procedure that if there is no activity
>> at the user level after 30 minutes, the database closes for that user. I
>> was thinking that maybe someone was rebooting the computer while a
>> database was open.
>>
>> Another thought was that there were network issues across the share
>> drives, but the network groups says that there is no indication of any
>> problems.
>>
>> I did not have this issue on Office 2003 and never once had to do a
>> restore. Now, on Office 2007, I am restoring the entire database and
>> copying tables at least once a week. We are planing on converting the
>> database to the new Access 2007 on May 11th to see if that helps.
>>
>> Any ideas or suggestions would be very helpful. I am at a complete loss
>> on this one. Thanks.
>
>

It does not remove it but will disable it. The choice is offered to each
user.


"Chuck" <Chuck NY 1958 @Yahoo.com> wrote in message
news:%(E-Mail Removed)...
>I know about the security features. It does prompt the user to enable the
>code and macros. It works when the user enables the code, but would it
>actually delete or disable it for all users if the person selects the wrong
>choice?
>
>
> "KC-Mass" <connearney_AT_comcast_Period_net> wrote in message
> news:(E-Mail Removed)...
>> It is all attributable to Access 2007's enhanced(?) security features.
>> It''s default behavior is to shut off all VBA code and Macros.
>> Google these groups for "Trusted Locations", "Access 2007 security
>> features", etc.
>> There are solutions. Changing to ACCDB will not fix it.
>>
>> Regards
>>
>> Kevin
>>
>> "Chuck" <Chuck NY 1958 @Yahoo.com> wrote in message
>> news:%23I$p%(E-Mail Removed)...
>>>I have an MDB that was developed in Access 2003 and now running in Access
>>>2007. It has not been converted to an ACCDB file format yet. The file
>>>is around 30MB with over 40,000 records that are used daily by
>>>approximately 200 users across a network. It is not split into a
>>>back-end or front-end. It is on a share network drive that everyone
>>>accesses. I cannot, for several reasons, split it and put a front-end on
>>>all the users desktop across the business.
>>>
>>> The problem I am having since upgrading to Office 2007 is that for no
>>> apparent reason, all the visual basic code vanishes. All the forms,
>>> reports, queries and tables seem to be fine, but the code is missing.
>>> We are running Office 2007 SP1 on all the computers. The database
>>> starts fine, the main menu appears, but nothing can be done afterwards.
>>>
>>> I first thought that nightly backups were corrupting it, but the start
>>> time of those were moved to a later time just to see if it made a
>>> difference. I put in a time-out procedure that if there is no activity
>>> at the user level after 30 minutes, the database closes for that user.
>>> I was thinking that maybe someone was rebooting the computer while a
>>> database was open.
>>>
>>> Another thought was that there were network issues across the share
>>> drives, but the network groups says that there is no indication of any
>>> problems.
>>>
>>> I did not have this issue on Office 2003 and never once had to do a
>>> restore. Now, on Office 2007, I am restoring the entire database and
>>> copying tables at least once a week. We are planing on converting the
>>> database to the new Access 2007 on May 11th to see if that helps.
>>>
>>> Any ideas or suggestions would be very helpful. I am at a complete loss
>>> on this one. Thanks.
>>
>>
>

It does not remove it but will disable it. The choice is offered to each
user.


"Chuck" <Chuck NY 1958 @Yahoo.com> wrote in message
news:%(E-Mail Removed)...
>I know about the security features. It does prompt the user to enable the
>code and macros. It works when the user enables the code, but would it
>actually delete or disable it for all users if the person selects the wrong
>choice?
>
>
> "KC-Mass" <connearney_AT_comcast_Period_net> wrote in message
> news:(E-Mail Removed)...
>> It is all attributable to Access 2007's enhanced(?) security features.
>> It''s default behavior is to shut off all VBA code and Macros.
>> Google these groups for "Trusted Locations", "Access 2007 security
>> features", etc.
>> There are solutions. Changing to ACCDB will not fix it.
>>
>> Regards
>>
>> Kevin
>>
>> "Chuck" <Chuck NY 1958 @Yahoo.com> wrote in message
>> news:%23I$p%(E-Mail Removed)...
>>>I have an MDB that was developed in Access 2003 and now running in Access
>>>2007. It has not been converted to an ACCDB file format yet. The file
>>>is around 30MB with over 40,000 records that are used daily by
>>>approximately 200 users across a network. It is not split into a
>>>back-end or front-end. It is on a share network drive that everyone
>>>accesses. I cannot, for several reasons, split it and put a front-end on
>>>all the users desktop across the business.
>>>
>>> The problem I am having since upgrading to Office 2007 is that for no
>>> apparent reason, all the visual basic code vanishes. All the forms,
>>> reports, queries and tables seem to be fine, but the code is missing.
>>> We are running Office 2007 SP1 on all the computers. The database
>>> starts fine, the main menu appears, but nothing can be done afterwards.
>>>
>>> I first thought that nightly backups were corrupting it, but the start
>>> time of those were moved to a later time just to see if it made a
>>> difference. I put in a time-out procedure that if there is no activity
>>> at the user level after 30 minutes, the database closes for that user.
>>> I was thinking that maybe someone was rebooting the computer while a
>>> database was open.
>>>
>>> Another thought was that there were network issues across the share
>>> drives, but the network groups says that there is no indication of any
>>> problems.
>>>
>>> I did not have this issue on Office 2003 and never once had to do a
>>> restore. Now, on Office 2007, I am restoring the entire database and
>>> copying tables at least once a week. We are planing on converting the
>>> database to the new Access 2007 on May 11th to see if that helps.
>>>
>>> Any ideas or suggestions would be very helpful. I am at a complete loss
>>> on this one. Thanks.
>>
>>
>

"Chuck" <Chuck NY 1958 @Yahoo.com> wrote:

>It is not split into a back-end or front-end.
>It is on a share network drive that everyone accesses. I cannot, for
>several reasons, split it and put a front-end on all the users desktop
>across the business.

Why not? You're in significant danger of corruption and wierdnesses
of the kind you describe.

Is it possible that some users are still using it on an older version
of Access?

Tony
--
Tony Toews, Microsoft Access MVP
Tony's Main MS Access pages - http://www.granite.ab.ca/accsmstr.htm
Tony's Microsoft Access Blog - http://msmvps.com/blogs/access/
Granite Fleet Manager http://www.granitefleet.com/

"Chuck" <Chuck NY 1958 @Yahoo.com> wrote:

>It is not split into a back-end or front-end.
>It is on a share network drive that everyone accesses. I cannot, for
>several reasons, split it and put a front-end on all the users desktop
>across the business.

Why not? You're in significant danger of corruption and wierdnesses
of the kind you describe.

Is it possible that some users are still using it on an older version
of Access?

Tony
--
Tony Toews, Microsoft Access MVP
Tony's Main MS Access pages - http://www.granite.ab.ca/accsmstr.htm
Tony's Microsoft Access Blog - http://msmvps.com/blogs/access/
Granite Fleet Manager http://www.granitefleet.com/

I cannot split it because we are a government agency that is told what to
put onto each desktop and we cannot change it. They consider placing a
front-end on each computer an "installed" program and it is not allowed.
Trust me... this has been an ongoing battle. They also will not allow a
trusted folder where I can put the database so each user does not have to
enable the code/macros each time.

I just put in the code to capture the Access version and build numbers as
part of the audit trail that is built into the database. We were thinking
along the same lines that maybe there is a rogue copy of an older version.
We recently installed SP1 so I don't know if there were any fixes for this
type of behavior. I don't know when SP2 will be pushed down to the
desktops.

I have searched the internet and stumbled across this same issue, but there
resolution didn't seem to fix the problem (decompile and recompile).

"Tony Toews [MVP]" <(E-Mail Removed)> wrote in message
news(E-Mail Removed)...
> "Chuck" <Chuck NY 1958 @Yahoo.com> wrote:
>
>>It is not split into a back-end or front-end.
>>It is on a share network drive that everyone accesses. I cannot, for
>>several reasons, split it and put a front-end on all the users desktop
>>across the business.
>
> Why not? You're in significant danger of corruption and wierdnesses
> of the kind you describe.
>
> Is it possible that some users are still using it on an older version
> of Access?
>
> Tony
> --
> Tony Toews, Microsoft Access MVP
> Tony's Main MS Access pages - http://www.granite.ab.ca/accsmstr.htm
> Tony's Microsoft Access Blog - http://msmvps.com/blogs/access/
> Granite Fleet Manager http://www.granitefleet.com/