info and questions on conversion to A03



Hi All,

I'm making a little, very little progress on this and have found some
info that may help others going down this road. Also, if you have ideas
and suggestions, please let me know. It's slow going reinventing the
wheel. :-)

Using ADO, OleDb.Jet.4 and v2.6 replication objects,I'm converting
client databases to Jet4 and then using Access to convert to Access
2003.

Of course, once converted, Access97 can no longer read the database.
However, neither can Access 2003. Talk about purgatory! Fortunately,
Jet4 can still read them so we're not completely dead in the water.

Access 2003 prompts to "open" or "Convert" when I try to open a
converted DB. "Open" bombs with three read-only errors. "Convert" seems
to work after a few read-only errors, but when I try to open the
re-converted DB, Access 2003 says it's an old format so we can't save.
Yes, these sound like MS bugs, but from how far back?

At the suggestion of a reader of this group, I tried "joining" the A03
Workgroup Administrator to the MDW from the Access97 machine. This
produced no errors, but also didn't help. But it did give me some ideas
to check out the table permissions in the Access97 DBs.

Opening the unconverted DB in Access97, I find that all the tables are
owned by Admin except some of the system tables. They are owned by
Engine. "Engine"? There's no user called Engine. No Engine group. We've
never created a user or group called "Admin", either, for that matter.
Obviously, some tool that considers itself to be an engine, took
control of the system tables. Jet03? Hmmm.

Making the system tables all owned and writable by Admin seems to be a
small step in the right direction. After converting one of these
databases, Access 2003 is able to open it, but only after it fails the
first time. That's right. It bombs the first time it tries to open the
DB, but then succeeds the second time.

Do these sound like bugs to anyone but me? :-)

So -- with this much background, can anyone guess what the real
required permissions/onwerships are for an Access97 database so it can
convert to Jet4 in a format that Access 2003 can successfully convert
and open?

-Dave

.



Relevant Pages

  • Re: ASA9 and multiple databases: best practise?
    ... The databases and the number of engines aren't directly related. ... database with an engine. ... You can affiliate tasks and CPUs to engines. ... Think of your server as a pool of tasks (one task per connection to the ...
    (comp.databases.sybase)
  • Re: Is MS Access A Toy?
    ... The Jet engine and the current Access 2007 DB engine that is derived from ... Jet are installed by default, and they are file-server database engines. ... Details of the difference between server and file-server databases have been ...
    (comp.databases.ms-access)
  • Envelopes ... need all caps
    ... databases from Access97 to 2003. ... have all caps in the addresses for our mail center to ... has taken care of changed information in the past. ...
    (microsoft.public.access.reports)
  • Re: no server engine, only local workstation engines, Status 116
    ... All the databases are version 7 due to history. ... Isn't it possible to adjust an local Pervasive engine as a LOCAL WORKSTATION ... no acception of remote requests ...
    (comp.databases.btrieve)
  • Re: ASA9 and multiple databases: best practise?
    ... Is this a question of how many databases to have per server, ... engine for each database or one engine driving many databases. ... see any benefit in maintenance by having several databases in one ...
    (comp.databases.sybase)