Copying data from access table

[Primoz]

Hi!
There's an unexplainable error happening when opening any of my DB in
Access 2003 under WindowsXP. My DB were made in Access 2000 under W98.
I installed WindowsXP recently. There's no conversion going on when
trying to open it in 2003 under WindowsXP and there's an error message
that something is wrong. (I checked and so far, thank God, nothing is
wrong, I mean, no data lost). So, I wanted to make a new DB and copy the
data from my older DB into it. While selecting ALL data (about 1.700
lines) and trying to copy it into the new table, it copies ONLY 32
lines. Besides, any new DB made in Access2003 has info it's made as
Access 2000.
So my questions are:
how come my Access 2000 DB is not converted into 2003 DB?
how come starting a new DB it is also mentioned it's made as Access 2000?
how come only 32 lines are copied while 1.700 lines in DB were selected
and copied?

Thanks for any help

Primoz

 

[Allen Browne]

It sounds like a corrupted index.

Make a backup copy of the mdb file while it is NOT in use.
Then open Access and try:
Tools | Database Utilites | Repair

If that does not solve the problem, open the Relationships window (Tools
menu), and delete any relations on this table. Then open the table in design
view, and remove any indexes other than the primary key. Then compact the
database. If this works, you can rebuild the indexes and relations again.

To tell A2003 which database format you want to use by default:
Tools | Options | Advanced | Default File Format

If you do make a new mdb file, rather than clipboard the data across, use
File | Get External | Import. And please turn off Name AutoCorrect before
you import the data. More info on why:
http://allenbrowne.com/bug-03.html

 

[Primoz]

Thank you for your help but....there's always a 'but', isn't it?
So...under tools in Access2003 there's NO Repair Option under the TOOLS.
So I tried convert to 2002-2003 (this is what itsays here) and I chose
the DB. And then I got a reply: "An error occurred and this feature is
no longer functioning properly. would you like to repair this feature
now?" And now comes the 'greatest part': If I click yes, then the Access
is installed again and the same option comes out all the time. If I
click NO, then I got it converted to 2002 - 2003 file format. And now
the 'funny' story goes on. When I try to open this converted file, I
first get this message: "The file may not be safe if it contains code
that was intended to harm your computer. Do you want to open this file
or cancel the operation?" If I chose OPEN, the TABLE is opened. It seems
it's ok. But why is there this message? why would I want to harm my own
computer? What's the point? But this is not the end of the trouble here.
If I close Access and open it again, then try to open ANY db-file, all
starts again: again I have to go through all the mentioned procedure and
clicking that there's no danger to harm my PC etc, the same thing as I
described up there.

I managed to make it 2002 - 2003 default under Option at TOOLS, as you
suggested but nothing changed after that.

I'm grateful you tried so hard but there's same thing going on and I
still can't START any new DB that would be in 2003 access format. it'+s
pretty hectic, I can say. Thanks anyway, maybe you have any more ideas,
if I'm not big trouble ?

Primoz

 

[Allen Browne]

Hi.

Sounds like there is a problem with your installation of Office 2003. If you
have the default menus, there should be a Repair on the Tools menu under the
submenu Database Utilities. (The security messages are "normal" - see
below.)

It might be worth following this sequence:
1. Check your disk for errors (e.g. chkdsk or scandisk),
2. Uninstall Office 2003,
3. Reboot.
4. Install Office 2003 again.
5. Log onto http://support.microsoft.com, and download any patches you need.

Regarding the security messages, these always occur in Access 2003. You can
avoid them by setting your security setting to Low under: Tools | Macro |
Security. I have to agree with your, "What's the point?" comment. Microsoft
is working very hard on security across the board, and deserves to be lauded
for the work they are putting into this area. However, this particular
application of security is about as useful as forcing bicycle riders to wear
seatbelts in my view.