Re: Migration and authorisations

Thanks for your reply.

You did not mention the database and version or anything like that so you
are probably not going to get much usable help.

It's an Access 2000 mdb and we now use Access 2002.

A lot depends on why you split the database up on the two drives. If they
are in two separate databases you may have two separate sets of security.
Some networking server software would let you join the two drives into one
volume and treat it all as one location or object if it was on the same
server.

I don't know how things were made on the former server or why. I only know
that the mdb and mdw are both in the same folder. This morning a co worker
copied the mdb and mdw to a C-drive and simulated the old path with the dos
substitute command. That didn't change anything: same message.

Seems we have to inform Houston and bring in the helicopters to hunt down
the creator of this database :-)

john

"Last Boy Scout" <BadBill@xxxxxxxxxxxxxx> schreef in bericht
news:EyoWh.2347$lq2.485@xxxxxxxxxxxxxxx
John wrote:
Recently we migrated to a new hard- and software environment. Also, all
data has moved to a new network drive, with a new name. We have one mdb
and an associated mdw that now gives us trouble. If the users try to open
the mdb they get the message (translated from Dutch):

"you do not have the correct authorisations for the use of object 'G:\...
\OurFileName.mdb '. Contact you system manager or the person who has made
the object, to establish the correct authorisations for you."

We suspect that there is hard path reference in the mdb that points to
the old location of
the mdw (with the old drive's name). I have never worked with
'authorisations' or working grouops and the builder of this application
is gone and can not be reached.

Does anyone have an idea on how we can get the mdb to run again? Even if
we would lose the whole autorisation and workgroup functionality in this
mdb, that would be better than nothing being able to access the mdb at
all.

Temporarily moving back to the old network drive is not an option.

Thanks in advance,
john
Either way you still have to know how to access the security settings. You
did not mention the database and version or anything like that so you are
probably not going to get much usable help. A lot depends on why you
split the database up on the two drives. If they are in two separate
databases you may have two separate sets of security. Some networking
server software would let you join the two drives into one volume and
treat it all as one location or object if it was on the same server.

My suggestion is hire a consultant that knows the database and/or
application or some kind of professional outfit that can make some
suggestions or help you to accomplish what you want to do. It may save
you money and time in the long run. You dont want to find out months from
now that you are going to have redo your conversion because you have
missing writes to the table and corrupt data.


.

Relevant Pages

  • Re: a question regarding separate mdbs in Access
    ... All of the rest put into a front end mdb including Queries, ... You can separate 'code' from the actual data. ... Access Database Application with compiled VBA'). ... MS Access when it comes to various 'developer' versions hasn't been quite as ...
    (microsoft.public.data.ado)
  • (no subject)
    ... - LDB locking which a persistent recordset connection fixes ... New format of Access 2000 MDB ... Place backend MDB on the root of the network share rather than several folders down ... Subdatasheets are a new feature in Access 2000 Therefore, you are more likely to notice this behaviour after you convert a database from an earlier version. ...
    (comp.databases.ms-access)
  • Re: Migration and authorisations
    ... Solutions Sample Database", the Solutions sample (which hasn't been ... It's an Access 2000 mdb and we now use Access 2002. ... Some networking server software would let you join the two ... why you split the database up on the two drives. ...
    (comp.databases.ms-access)
  • Re: temp db
    ... If the database is not in use, you can create a copy just by copying the MDB ... The purpose is to create a temp db for all the ... ' This subroutine illustrates how to use a temporary MDB in your app. ...
    (microsoft.public.access.formscoding)
  • RE: Access to Access Automatic Updates
    ... Then navigate to the database from the File Open dialog and open it. ... You will need to do it for mdb that has tables you need ... MS Office Master 2000 ed. ... you will need to create a form that opens on ...
    (microsoft.public.access.externaldata)