Susanhopes
Technical User
I hope someone can help me find the end piece to start untangling this mess.
Today I began moving over my multi-group secured, replicated dbase to a new platform in an attempt to leave behind some corruption. We're using all the built-in tools for these two procedures. No server, using networked PCs and a VPN to another ofice. My workstation is not the home drive of the working copies, my main user has it on her hard drive.
We synchronized all replicas, made a backup of the Master to my hard drive, and I got to work using the detailed instructions I used originally several years ago, from a user here from AlphaBet City Dataworks.
The trouble began when I imported objects from the old dbase, via the backup copy so I wouldn't infringe upon the ability of my users to use the old replicas as a reference only. A number of objects wouldn't import, I think because the superuser identity that I created as an initial step didn't have permissions for all of the groups that existed on the old dbase, those that were created after the initial setup. (I actually use a different identity when I work, and keep the superuser as a backup.) The import hung, I had to end the task manually, then had to go pick up a sick child and returned to work this afternoon.
When I got here, I found one user logged into but not using the working replica, and other users trying to log in were told they didn't have permissions. There were lock files on the working dbase and systemdbase, and those went away when last user logged off. Probably result of being hung up during import- even though I wasn't using that replica as the source for the import and none of them have exclusive use permission?
Now I have no ability to get into the old master, replicas, or their backup. I have an incomplete new dbase that opens without asking for logon (most of the time), and security screen switches between showing no security set, the old list of identities and groups, and the one I began earlier today, changes when I reopen the file. It gives me the Admin identity, from which permissions were revoked as a step in setting up security.
Also, though I've been using Access 2003 for many years, this new dbase created in 2000.
I need to 1. Import the missing objects
2. Get the new dbase to secure and ask for a logon consistently
3. Figure out which copy of the systemdbase the thing is referencing so I can identify and distribute it correctly. Was hoping to call it systemdbase2 for clarification.
4. Figure out if there's a problem with the workgroups that is causing all this.
Can someone please help?!! I have secured a backup from the other office which is being held off the network and can start over but am worried that the workgroup files are too tangled to do that and this might happen again if I use them here. Problem when transferring files from one complexly secured dbase to another, diferent from initial setup. Thank you a million times over.
Susan
Today I began moving over my multi-group secured, replicated dbase to a new platform in an attempt to leave behind some corruption. We're using all the built-in tools for these two procedures. No server, using networked PCs and a VPN to another ofice. My workstation is not the home drive of the working copies, my main user has it on her hard drive.
We synchronized all replicas, made a backup of the Master to my hard drive, and I got to work using the detailed instructions I used originally several years ago, from a user here from AlphaBet City Dataworks.
The trouble began when I imported objects from the old dbase, via the backup copy so I wouldn't infringe upon the ability of my users to use the old replicas as a reference only. A number of objects wouldn't import, I think because the superuser identity that I created as an initial step didn't have permissions for all of the groups that existed on the old dbase, those that were created after the initial setup. (I actually use a different identity when I work, and keep the superuser as a backup.) The import hung, I had to end the task manually, then had to go pick up a sick child and returned to work this afternoon.
When I got here, I found one user logged into but not using the working replica, and other users trying to log in were told they didn't have permissions. There were lock files on the working dbase and systemdbase, and those went away when last user logged off. Probably result of being hung up during import- even though I wasn't using that replica as the source for the import and none of them have exclusive use permission?
Now I have no ability to get into the old master, replicas, or their backup. I have an incomplete new dbase that opens without asking for logon (most of the time), and security screen switches between showing no security set, the old list of identities and groups, and the one I began earlier today, changes when I reopen the file. It gives me the Admin identity, from which permissions were revoked as a step in setting up security.
Also, though I've been using Access 2003 for many years, this new dbase created in 2000.
I need to 1. Import the missing objects
2. Get the new dbase to secure and ask for a logon consistently
3. Figure out which copy of the systemdbase the thing is referencing so I can identify and distribute it correctly. Was hoping to call it systemdbase2 for clarification.
4. Figure out if there's a problem with the workgroups that is causing all this.
Can someone please help?!! I have secured a backup from the other office which is being held off the network and can start over but am worried that the workgroup files are too tangled to do that and this might happen again if I use them here. Problem when transferring files from one complexly secured dbase to another, diferent from initial setup. Thank you a million times over.
Susan
