This is further information on my posting about converting Access 2010 to
Access 2003 I have just removed and re-installed Office 2010 32 bit on my
Windows 7 machine. If I create a completely blank database (Database9.AccDb)
- no tables, no forms, no VBA and try to Save & Publish in Access 2003
format, I get an error message message "Could not use 'C:\Phil
Data\Access\Database9.AccDb'; file already in use" . If I add any tables, the
error is the same

I have Access 2010 running under Windows XP on another machine, and the
conversion of a genuine BE Db (Tables only) went without a hitch. Anyone else
found the same problem? Phil

Phil was thinking very hard :
Sounds like a Windows 7 Permissions issue to me. Are you an Admin on
this machine? Does the Folder "C:\Phil Data\Access" have full RWUD
permissions for all users? What happens when you start Access using
Run as Admin? All of the above is just a guess. I do not have an
Access 2010 to test.

Rdub

"Phil" wrote in message news:j2bht4$nii$1 (AT) speranza (DOT) aioe.org...

2010 can create a mdb file.

Launch 2010, you be on the main page with options to database from templates
etc.
On the left side, click on options, under general, change the default file
format to 2002-2003.

When you click ok, now you are back to the main startup, and on the right
side, your default database should be Database1.mdb or DatabaseXX.mdb
whatever.

So you can thus create the 2003 format database. After you create, then
simply import data from the other database.

However, you should not be needing to do all this workarounds, but it at
least good to know.

And while we are at this, I would perhaps we manually type in a name here in
place of some default Database9 which might in corrupted, in use or some
other issue.

So, before you even try the above 2003 mdb idea, I would create a new blank
database ACCBD format, and then import the data from this Database9.ACCDB
that seems to be giving you trouble.

So try creating a new blank database (accdb) with a different name, and then
import the data from Database9.
Looking at this, it seems like perhaps Database9.accDB is damaged here.

(and, while we are at this, give the machine a re-boot before you try this).


--
Albert D. Kallal (Access MVP)
Edmonton, Alberta Canada
Pleasenospam_kallal (AT) msn (DOT) com

On 16/08/2011 03:26:21, "Albert D. Kallal" wrote:
Albert, you're a genius

Worked a charm.

However it seems to be an Access 2010 / Windows 7 problem as everything works
as expected with Access 2010 / Windows XP on my other machine. Difinately no
corruption problems as Database 9 was a new completly empty test database.
(also tried it with another test Database 8 with the 1 default table in it
with 1 line of data).
The Access Folder & Sub Folders are all trusted locations and I have full
admin permissions.

Trying to find out if any other users have had this problem or whether it has
worked for them, in which case, it is something peculiar with my Windows 7
machine

Thanks again

Phil

"Phil" <phil (AT) stantonfamily (DOT) co.uk> wrote in
news:j2d9qu$epd$1 (AT) speranza (DOT) aioe.org:

But in Windows 7, by default, you run with a USER security token,
not an ADMIN security token. That's the whole point of UAC.

What permissions do the regular users have? They need full control
on the folder.

--
David W. Fenton http://www.dfenton.com/
contact via website only http://www.dfenton.com/DFA/

On 17/08/2011 20:50:29, "David-W-Fenton" wrote:
Ah..., I think a misunderstanding David.

When I refered to "users", I meant anyone out there using Windows 7 and
Access 2010 32 bit.

Phil

"Phil" <phil (AT) stantonfamily (DOT) co.uk> wrote in
news:j2ifpa$38d$1 (AT) speranza (DOT) aioe.org:

So do I. When you're running in Win7 as a user logon that is in the
Administrators group, Win7 runs all processes with a user-level
security token, which means that any time the process needs elevated
privileges, you are asked to approve it (i.e., the UAC prompt).
However, UAC does not kick in for file system permissions, so if
you've placed your Access file in a location that only
administrators have full control of, you won't have full access to
it unless you explicitly run your program as administrator (i.e.,
with an admin-level security token, instead of the default
user-level token).

What this means is that you must apply permissions to your files
that give full access to USERS, not just to administrators.

--
David W. Fenton http://www.dfenton.com/
contact via website only http://www.dfenton.com/DFA/