Hi All,
With the help of many people on this forum, my database is coming along well (Thank you!). My DB will end up on a server where it will be accessed. My question is; should I use the replica function, or back up the file every day or so.
The database I am replacing has been a replica and it always looses data. I am not sure it is because its a replica or not.
Any thoughts?
Bones
I am still new to Access and am loving the learning process. I am stuck on a problem though. I have serached the forums here and various other places and haven't found the info I am looking for. I was wondering if there is a way to have a relpica (or a seperate database that can syncronize) that has a modied design. I want the main one to have everything on it, reports/forms/ add/delete/ect, but I want another one that is simply a data entry form, with only the option to input data. I would love to do this and avoid system security measures with usernames and passwords. From my reading it doesn't seem like I can do this, but I still hold in my heart a glimmer of hope. Please help, and if you can explain the process to me, all the better (its how I'm learning).
View 1 Replies View RelatedHi
Am using a replica set in order to distribute a school reporting system around teaching staff.
Everything works fine apart from one thing. A marking system (basically 1 to 6 list) is stored in a linked table. Before replication this appears in the correct order. Once the database has been replicated however the list is placed in a random order and I cannot rectify this.
With only 6 items this is not much of a problem but I also want to use a much longer list and the same problem appears.
Can anyone explain why this happens and if there is a simple way to get around it?
Am really only an Access novice and I really appreciate any help that you could give me.
Cheers
Mike
I know how to setup a Replica's Priority, but where do I go if I want to change it afterwards? I have searched everywhere, or am I just supposed to create another replica and set it then?
View 2 Replies View RelatedI need the same database as managed and unmanaged in repl manager, I think.
My replica set got scrwd up and now I need to re add an unmanaged replica.
Previously the map displayed a scheduled synchronization line to the replica not managed by synchronizer.
I can add the unmanaged replica, but how do I add the synchronization line?
Do I need the same replica added to the map 2x? 1 managed and the other unmanaged?
i tried uploading 2 bmp files to show the way it was and is now but i dont see them, how do u add bmps to post?
Love this forum! It orginally helped me build a database to manage customers back in 2002 (using Access 2002). Becuase of our slow server, I was forced to spilt the database and it's been great for years (some glitches). Recently one of the users upgraded to Access 2003. When he sync's to the master file, the master has problems. "...contains a missing or broken reference to the file 'OWC10.DLL' version 1.1" I reviewed the references and it's looking for Microsoft Outlook 11, instead of 10. When other users sync, everyone now inherits this problem. Do you have any ideas for a solution so I don't have to fix reference problems? All users will eventually be on Access 2003 so having him stop using it would only be a temporary solution. Is there a patch or upgrade to fix this problem? Any help? thanks in advance....
View 1 Replies View RelatedI currently have a database thats A Replica which I need to Convert Back to a Normal Data file, Is there a simple way of doing this other than creating a new db with tables then using Querys to add the data from the replica.
I'm using 2002 and the replica if sized around 470Mb with over 200 Tables.
also does anybody know if the file size for assess 2002 was incresed from access 2000's 2Gb.
thanks
mick
I am getting this error on a access 97 database that we have been using for years. the message just started popping. use are still able to access the database, yet this message will not got away.
this member of the replica set has expired because it hasn't been syncronized with another m ember of the replica set.
Using access 2003 my replica set tables in both the master and replicas seems to have lost the key field! The data and field itself are simply missing from every table. When I look at the data in the tables the key field called 'UID' is not visible but I can still see it in the relationships view and in certain forms and queries. If I try to re join any of the two tables the UID field comes up as an option to join the two with but it's still not visible in any of the tables.
View 1 Replies View RelatedI recently was asked to update a client's BE & FE database.
It seems the client only has a replicated version of the database. I don't have the original Design Master.
Problems with negative autonumbers (it seems are due to replication), made me want to remove all need for replication from the database sets.
I attempted to modify some of the Tables in the BE and keep receiving the same error when I try to save it:
ERROR: "You cannot make changes to the design of the database at this replica"
I haven't found a solution on the forum yet. Any ideas?
I found the Replication part of this Microsoft KB article somewhat helpful: http://support.microsoft.com/kb/275561/en-us
Hello I have a perplexing problem …
I have been using replication successfully for years. Recently the PC where my Design Master resided crashed taking the hard drive with it. No problems I thought, I used a replica to recover the design master and placed it on the new hard drive (the OS and Access was upgraded from 2000 to XP, however the Access 2000 file format was retained – there are still a couple of laptops with only W2000 software). I understand that moving the path of replicas or design masters is no no, so I proceeded to start from scratch and create a complete new batch of replicas based from the new design master.
Everything was going to plan UNTIL a replica was routinely synchronized with the design master. The design master reverted back to a replica. I recovered the design master again, everything looking fine until again a synchronization causes the design master revert to replica.
Next plan of attack to hopefully fix a potential corruption problem: create a new blank database, import all (non-system) tables, compact and repair, and create a new replica from scratch. From the design master, I created the complementing replicas and sure enough the Design Master again reverted to a Replica after a routine synchronization.
I repeated this “start from scratch” procedure, and the same results prevailed. I am at a loss especially since I verified that the hidden system MSysReplicas table had only two entries after the Design Master and Replica were first created.
I would greatly appreciate any ideas of where to go next with this problem.
Thanking you for your time.
I have a replica at work, 1 copy on the network, 1 local.. I need to add a column to the main table, getting "Operation is not supported for this type of object".... I have users that use the database but was given a change to the form/report which requires a column addition. What is the simplest way to get around this??? I'm trying not to get into major problems.
View 1 Replies View Related