split database doesn't work now (converted from xp to 2000)

[Lee Johnson]

Ok, this is a wierd one:

I developed a database in XP which is going into production in 2000.
Testing on both systems (I would convert the database to test on the
production system) was flawless. Ready to go live, I split the database
then converted it to 2000 (front and backend) and threw it on the production
system. Now I can't view the table in Datasheet view and I can't access any
recordset.

I went back to the master (which is in xp but is now split) and imported the
tables to create a single database again. I then created a copy in 2000 and
trew it back on the production box. Same problem even though this is, in
theory, the same as the the original that worked fine in testing.

I have no problem viewing either version in XP of course. I don't see any
permission issues.

I'm stumped, any ideas.

Lee

 

[Karl Burrows]

Why did you convert it to 2000? 2000 and XP run basically the same. If you
were going from 97 to 2000/XP, you would have to. Try running the same XP
file in 2000 and see how it does. I use 2003 now and have been working on
databases used by Office 2000 users with no problem in XP and 2003.

 

[Allen Browne]

In your Access 2000 front end file, delete all the linked tables.
Then link them again to the new Access 2000 back end:
File | Get External | Link

 

[Lee Johnson]

Well, an Access XP database (2002) will not work in Access 2000, so that
won't solve the problem.

But thanks,

Lee

 

[Lee Johnson]

I did that already and it didn't work. In fact, even the backend itself
won't allow me to view the table in Datasheet view (although no problem with
design view).

Lee

 

[Lee Johnson]

I split an Access 2003 database. I converted the backend to Access 2000.
When I open the backend and try to view any table in Access 2000 I get
"Microsoft Access can't open the table in Datasheet view." I can view the
tables in design view thought.

Lee

 

[Albert D. Kallal]

when you look at all the tables on the table tab in the back end...are there
little arrows on each table? (if yes..then your back end is not a backend!).

From what you describe, it looks like your back end mdb is not really a back
end, but in fact had links to some other mdb file.

You could check this hitting ctrl-g, and in the debug-windows type:

? ? currentdb.TableDefs("tblAnswers").Connect

If you do the above in a front database, it will show you the path name to
the back end....try this.

If you do the above in the back end database..then nothing should show....

 

[david epsom dot com dot au]

As I understand it, your A2K database, split or unsplit, does not work
on your production PC.

Does any other A2K database work on your production PC?

If you compact the A2K database does it work?
If you compact the A2K database in XP does it work?

Do you have read-design permission but not read-data
permission on new tables?

(david)

 

[Lee Johnson]

the database worked fined on the production PC before I split it. After I
split it it wouldn't work. Even now that I have re-assembled it it doesn't
work.

I've tried compacting it on XP and that didn't help. I will try compacting
in A2K. As far as the permissions go, the permissions (Tools\Security\User
and Group Permission) are all fine.

I'm starting to wonder if there's been some form of coruption that occured
when I split then converted (and compacted) the database.

Lee

 

[Karl Burrows]

I'm not sure why. I do it all the time. I program and build it here and
just take over to the site to replace the existing file with no problems.