Group:  Microsoft Access ยป microsoft.public.access.setupconfig
Thread: Access 2007 Bugs and Data Corruption in Windows Vista

Geek News

Access 2007 Bugs and Data Corruption in Windows Vista
"NZSchoolTech" <nzschooltech[ at ]education.nz> 12/4/2008 6:32:46 AM
We have been developing several databases in Access 2007 this year and have
noticed several bugs or serious problems that Access 2003 does not have.

1. In an Access 2007 report, a calculated field will sometimes randomly
refuse to display its calculated result and will display ?Name instead. No
problem occurs if the report is opened in Access 2003 (for a database file
in Access 2000 or later format)

2. Access 2007 will sometimes give errors about something like the old
MSBasic errors from Dos days that I remember, the message goes something
like "Return without Gosub" and that is when calling code in a form, an
event procedure for a specific control on a form, when the same database
(Access 2000 or later) is opened in Access 2003 no such problem occurs.

After the instance of the first problem I turned off Automatic renaming
which I found advise about on a website, however the problem was not
totally resolved for Access 2007 and we have used Access 2003 to resolve the
problem as a work around.

3. The most serious issue we have encountered on Vista systems in particular
is corrupted databases on files accessed over a network share, which just
about never ever happens on XP. And I am not talking about multi user
databases, I am talking about a single user database that only I use. When
this started to happen I looked on the net to see if other people had the
same problem, and sure enough, if they had a Vista user accessing their
database, then they had, and they had the same sitation as us of no problems
with database corruption before Vista.

I wrote more information about this in my personal blog at
http://nzschooltech.blogspot.com/2008/08/windows-vista-and-microsoft-access.html
You can comment there or here as you wish. The important points being
- This problem never occurred on XP
- THis problem doesn't occur if Vista accesses the database on the local
hard drive
- Both Access 2003 and Access 2007 get this corruption problem the same way
on a Vista machine when the file is accessed over a network
- I do not use bookmarks in this database. It is very simple except for a
couple of calculated fields that run DAO queries and do a calculation from
the data that the query returns. They do not write data into any fields of
the database, and do not use bookmark objects in the DAO code.
- My PC has the Vista and Jet latest service packs and all available
updates.

--


Re: Access 2007 Bugs and Data Corruption in Windows Vista
"Gina Whipp" <NotInterested[ at ]InViruses.com> 12/31/2008 4:09:49 AM
I just a reason why 2. might be happening... DoCmd.Requery caused this
error in 2007 but not in 2003.

I have noticed that Access 2003 or less is more 'forgiving' then Access
2007.

--
Gina Whipp

"I feel I have been denied critical, need to know, information!" - Tremors
II
"NZSchoolTech" <nzschooltech[ at ]education.nz> wrote in message
news:euxnoodVJHA.5504[ at ]TK2MSFTNGP05.phx.gbl...
[Quoted Text]
> We have been developing several databases in Access 2007 this year and
> have noticed several bugs or serious problems that Access 2003 does not
> have.
>
> 1. In an Access 2007 report, a calculated field will sometimes randomly
> refuse to display its calculated result and will display ?Name instead. No
> problem occurs if the report is opened in Access 2003 (for a database file
> in Access 2000 or later format)
>
> 2. Access 2007 will sometimes give errors about something like the old
> MSBasic errors from Dos days that I remember, the message goes something
> like "Return without Gosub" and that is when calling code in a form, an
> event procedure for a specific control on a form, when the same database
> (Access 2000 or later) is opened in Access 2003 no such problem occurs.
>
> After the instance of the first problem I turned off Automatic renaming
> which I found advise about on a website, however the problem was not
> totally resolved for Access 2007 and we have used Access 2003 to resolve
> the problem as a work around.
>
> 3. The most serious issue we have encountered on Vista systems in
> particular is corrupted databases on files accessed over a network share,
> which just about never ever happens on XP. And I am not talking about
> multi user databases, I am talking about a single user database that only
> I use. When this started to happen I looked on the net to see if other
> people had the same problem, and sure enough, if they had a Vista user
> accessing their database, then they had, and they had the same sitation as
> us of no problems with database corruption before Vista.
>
> I wrote more information about this in my personal blog at
> http://nzschooltech.blogspot.com/2008/08/windows-vista-and-microsoft-access.html
> You can comment there or here as you wish. The important points being
> - This problem never occurred on XP
> - THis problem doesn't occur if Vista accesses the database on the local
> hard drive
> - Both Access 2003 and Access 2007 get this corruption problem the same
> way on a Vista machine when the file is accessed over a network
> - I do not use bookmarks in this database. It is very simple except for a
> couple of calculated fields that run DAO queries and do a calculation from
> the data that the query returns. They do not write data into any fields of
> the database, and do not use bookmark objects in the DAO code.
> - My PC has the Vista and Jet latest service packs and all available
> updates.
>
> --
>
>


Home | Search | Terms | Imprint Contact
Newsgroups Reader - provided by WiredBox.Net