I have a replicated access database, and I want to move the design master to another computer. I have tried using the Windows 'Copy and paste' command, and the 'Save as' command, both result in creating a replicated database.
I have also tried chnging the design master status to a replicated database, but then I am unable to view any VB code behind the controls when I go to design view.
I have a database with 8 tables. When I create a replica, one of the tables (only one) in the replica gets modified such that Data Type for all the fields is Calculated, with the effect that the data cannot be changed by the user. The table design is not changed in the Master. What the heck? Of course the table design cannot be modified in the Replica, and there's no reason to modify it in the Master. A second replica on a different server had the same result.
I have a problem retrieving my Design Master. I regularly backup my DB onto a separate hard drive. And in doing so have lost my designing capabilities. I have tried replicating and retrieving the DM per the help section, but I receive numerous error messages telling me Error accessing file, network connection lost rollback error, etc. Any ideas would be greatly appreciated.
I appologise but I am useless with Access but am trying to learn.
I have a datababse that we use to log calls onto, There are five members of our team and each member has thier own replica of the datababse. At the end of each day we have to re-sync our replicas to the design master.
It would be nice if we could put a button on the form we use to do the synchronization for us. Is this possible and how do you do it? bearing in mind that I am not too good with access so I need laymans terms.
I am trying to replicate a database for mobile working. When I attempt to 'create a replica' I get this error:
"MS Access can't convert to design master Cannot make the Table "[TableNameHere]" object in tables container replicable."
The table in question is fairly large and has 248 columns and is linked to 3 other tables of similar size as well as 3 smaller ones. Got about 2000 or so records and set to cascade deleted and updated records. 248 columns should leave enough spare columns for replication though, shouldn't it?
Any suggestions as to what I should look for to fix this?
I have an application that when in design master shuts down when I attempt to open a certain form. I have traced the problem to a linked field from another table, by creating a new form and ommitting the said field, problem is its a required field!
If I copy the database (Backup) and run it as a replica it does not happen, if I then convert the replica to design master it happens.
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.
I am using Access 2003. I have developed a split (front and back ends), replicable database. As I make changes to the design master, I want to either keep old copies of the design master or ideally, maintain the design master under source code control (e.g.:CVS). This would allow me to be able to retrieve older versions of the database. The problem occurs what I make a copy of the design master, or when I try to pull out of my source code control system (CVS) an older version of the design master. When I open any of these copies, Access thinks this database is a replica and will not let me make any changes to the design.
Is there a way around this problem?
Or am I trying to do something in Access that does not make sense?
How to structure some MS Access 2007 Forms for the following scenario.
My table structure is as follows:
Product ++++++ ID (pk) ProductName ...
Tag ++++ ID (pk) TagName
ProductTag +++++++++ ProductID (fk) TagID (fk)
I want to have a main form that allows me to search for and displays a list of all products (and the dozen or so attributes for each product) that meet that criteria (I'm thinking a continuous form view of products).
So far so good. No problems.
Now I want a "tagging" form to the right of my continuous forms product list that is linked to the product which currently has focus. The tag panel should always show a complete list of all Tags. I want a checkbox next to each tag that I can switch on and off whether that tag applies to the currently selected Product. I also want to be able to add tags on the fly (without leaving the main form).
I think I have three forms in play :
Main Form Product Form (subform to Main) my product search criteria is probably on this form header. Tag Form (also subform to Main)
But with this approach I'm have trouble linking the two sub forms to each other. Actually, I'm having huge trouble figuring out how to display the list of all tags with a check box that when checked on and off creates / deletes a record in the ProductTag table and I really want Access to do as much of the CRUD as possible. I would prefer to avoid writing screeds of SQL INSERTS/DELETES on events. Am I asking too much of Access?
Hi there. I need a way to pass data between forms, and subforms. I have "form1" which simply contains a text box requiring the user to input an ID which I will call "PID". it also has a button which has the following code:
Private Sub Command5_Click() On Error GoTo Err_Command5_Click
Dim stDocName As String Dim stLinkCriteria As String stLinkCriteria = "[PID]=" & Me.PID stDocName = "TestExam" DoCmd.OpenForm stDocName, , , stLinkCriteria
On the form testExam, I have a page control with 3 separate tabs. For each tab, I've embedded three separate subforms. All forms involved, including the container form (testExam) are bound to separate tables. All tables have one common field - PID I'd like the user to only have to input the PID on one form, and have it trickle down to all subforms.
In the FOrm_Current sub of the testExam form, I have the following code:
Private Sub Form_Current() [PID] = Forms!frmForm1.PID End Sub
Using this code, I am able to pass the data from Form1 to testExam, have the PID on testExam filled in and on tab 2. But tab 1 will not populate automatically. I have no idea why. I don't know where to start troubleshooting this. Please help.
Is this even a good way to pass data between subforms?
I created a form through the form wizard in access 2007 and based it off fields in a table. the form is done but if I want to move the controls in the design view... I dont have the ability to move just one. I can either move all of them or none of them. Is there a way to change that?
I have received a replicated db --- that is all (not a master) I want to know if any one has experience in "unreplicating" a db and what steps I take to unreplicate this db. I know (more or less) what replication does for you, but I have never done it !!
Thanks to the many of you who have helpped me get this far. I am finally ready to deploy my database! I would not have gotten this far in just a few months if it were not for your helpful advice. :D One of the final stages is to place the database on the organization's server and to put FEs on each of the work stations. I've read a bit about replication and splitting of databases but I have one question I haven't found answered here...
What is the best time line for doing this?
Do I replicate the data base and then split it? Or do I split the data base and then make replicas of the FE?
Does it matter?
Also - is replication truly needed for all data bases - I have a test copy in which I split the Access file, then just copied each front end to 2 machines and it seemed to work okay. Am I missing something that will come back and "byte" me in the keester?
Many thanks again for previous help and for your answers to this question.
Need some advice on Replication of a backend mdb please. I currently have a client/server app - works great. The users now need to collect data from their internet as well as entering data themselves in-house. Situation... can not link tables from web mdb file IS dept forbids link through firewall. How might I be able to keep the data synchronized when the original backend resides within the firewall on the file server and the other needs to sit on the web server? OR ... is there another approach to allow data entry from both the internal users concurrently with data entry from the web. I'm scratching my head and my deadline is looming. Any advice is greatly appreciated.
hey there i want to make a MDE compression/compile but i get a msg that i cant compile a replication how the f*** i remove the replication, cuz i no longer own the master file
I am working with a database that uses an autonumber Data Type in it's tables, this field is set to 'Replication ID'. I am adding records to my table but for every record i add i need to retrieve the newly added primary key (which is the autonumber replication id). If it was a incrementing id i could simply select the MAX value from the field. But seeing as it's a replication id it won't bring me back the latest field. In SQL Server I would use the @@Identity function to return the id. Can anyone help me?
I am having multiple user problems with access 2000 quite frequently, and I thought that replication would solve this, as it stands however its proving difficult to get my hands on the developer edition, just wondering, is it worth the hassle to get it, or is there an effective alternative to replication?
Hi, I've been reading about this alot today but can't decide for sure if I should replicate my database or not. The users will have a front end installed on their local drive and the back end is on a shared server.
Basically the users will not be able to add or delete records. However, they can update one column- its a checkbox that allows them to select a record or records in a continuous form. I imagine that if 2 users were using it simultanuously and one de-selected all the records, they would be deselected on the other persons form? This is why I think I need a partial replica. That way when the user opens the database they get a fresh copy of the new data and can select and deselect drawings without interfering with others.
All records are automatically selected when the form is opened so updating changes in the master is not an issue.
Please let me know if I'm on the right track here..
I have a Design Master that I use for many replicas. I would like to replicate the design master so experimental changes to queries and tables can be conducted without exposing the "real design master" to errors? Each time I replicate/copy the design master the replica/copy will not allow changes. Is there a way to disassociate the copy/replica from the Design Master so experimental changes will be allowed and can be made? thanks
Allrighty, some questions about replication. I have gotten the Replication Manager from the helpful IT folks here, have made the database, and it works well to synchronise between different files locally on this computer. However, ideally the other people in the department would be able to carry replicas around on their laptops, while ideally the design master and overall database tidying should sit on mine. The setup is typical intranet here - computers are invisible to one another directly, and so are their virtual My Documents drives, while shared network folders are visible to all.
Questions;
1. Since I can't see any of the other laptop drives, and the database would have to be accessible offline, I assume indirect synchronisation is the only choice, correct?
2. Does the Replication Manager need to be installed on each of the laptops that will use the database offline?
3. If yes, what's the process? Do I install RM on each laptop, then use the Create Replica function to create one locally on each? No hidden pitfalls here?
4. If yes, is it sufficient to keep RM shut all the time unless specifically wanting to synchronise? Would happen at least once a week.
5. If Replication Manager doesn't need to be installed on other laptops, how do I move replicas there? I tried moving one through copy/paste, but that broke the link to the Replication Manager.
6. (Optionally - I've seen some references to 'replica farms' - what is that?)
Very much appreciated if anyone is able to answer..
I have a database accessed by alot of people and have recently added user level security so that i can monitor who is logged on etc.
Another thing i need is the ability to update the design of forms whilst people are on the database. To do this i planned on creating a replica and synchronising any changes after i had made them.
However, this is causing problems with my security. I cannot create the shortcut needed to give people access to the replica, they can only access the design master, which defeats the point!
It's me, yet again! This database I have built for the hospital I am employed by is almost ready for distribution. The only thing I have yet to do is set up securities for each of the medical directors.
For example, I don't want the ICU/Cardio-Telemetry Director to be able to view employee data for the Emergency Room staff and vice versa. I tried once at the very beginning to do a mock replicated database just to see if I knew what I was doing, and frankly, I didn't, not even at all! Should I set up replicas on the network for each director with only their little (or huge) bits of information, or should I setup securities or both, or are they the same thing?
I tried to do a new workgroup and set up groups and users there, but when I tried to log in as someone else, it didn't work. Any ideas? Thanks!
I created replication through Access, but when one of the users try to update a record he was getting the message Record deleted. So i search the internet and found that the solution of this error message was to Compact and Repair the database. When i did that i lost the replication, and now i can't create it back because there records on the database and i am getting an error message.
Any suggestions how to recover the database? By the way is the master database not one of the replicas.
Is replication causes these kinds of malfunctions?
