replica database 2000 Results

Sponsored Links:

I have never made a replica of a database. I have a laptop that would like to enter data into the database and then synchronize with the "main database" later. I'm finding bits and pieces of information on replication, but nothing that gives me step by step instructions on how to do this. Can you help me please?


I need to be able to pick up the file path of where the Access DB is residing. I used to be able to do this ok when using DAO, i.e. I would do the following:-

Dim db As DAO.Database
Dim strfilepath As String

Set db = CurrentDb
strfilepath = db.Name

This would return the full path of the DB's location:- Q:LloydsGreenwich2003 Q4994i - FSA return994_2003 Dec03.mdb

However, using ADODB, this no longer works.

The only alternative I can seem to find at present is the following:

Dim dbs1 As ADODB.Connection
Set dbs1 = CurrentProject.Connection

Which when interrogated gives me:
Provider=Microsoft.Jet.OLEDB.4.0;User ID=Admin;Data Source=Q:CotesworthAscotPremIncomeDatabasesPremium Income Monitoring.mdb;Mode=Share Deny None;Extended Properties="";Jet OLEDB:System database=C:PROGRAM FILESCOMMON FILESSYSTEMSYSTEM.MDW;Jet OLEDB:Registry Path="";Jet OLEDBatabase Password="";Jet OLEDB:Engine Type=5;Jet OLEDBatabase Locking Mode=1;Jet OLEDB:Global Partial Bulk Ops=2;Jet OLEDB:Global Bulk Transactions=1;Jet OLEDB:New Database Password="";Jet OLEDB:Create System Database=False;Jet OLEDB:Encrypt Database=False;Jet OLEDBon't Copy Locale on Compact=False;Jet OLEDB:Compact Without Replica Repair=False;Jet OLEDB:SFP=False

Which as you can see is far too much information!

How can I just pull the file path alone?



I am getting a 'Cannot open database ... It may not be a database that your application recognises, or the file may be corrupt' message whenever anybody tries to synchronise with a replica that forms the centre of a replication hub. I also get a similar message when I try to open the replica directly. The Design master is not part of the replication scheme and is not useful as a source of backup.

I think I recall from going through this once before that if I let Access repair the replica then it will work as a database again but still will not synchronise. Am I right about this and, if so, is there anything else that I can do? If I restore the replica from backup will the other replicas re-synchronise correctly or will they 'think' that they have already synchronised their changes and not update?

Incidentally, I read the backup strategy suggested in replies to the earlier post from Rosanne and it looks like very good advice that I will instigate asap.

I have a database that has been working fine for 6 months.
Recently we got the error

Index not found

When attempting to synchronise the master
with a replica.
There is no indication at which point, or which table or record that the missing
index occurs in. It doesn't even say which database.
Fantastic error reporting from Microsoft eh....

The synchronisation fails at this point with no come back.

I have tries a compact and repair, and this works fine
but makes no difference to the synchronisation error.

Anyone got any ideas or experienced this before?
I would love an answer, even if it is just to say

Go get the last good backups fella.

I have attached a copy of the error screen.

Thanks in anticipation

I just started working on a new project and it is still in the planning stages. I want to be able to limit access for a group of employees to a single form, where others would have access to the entire set of forms in the database. This project will be in the form of a Replicated Access Database (potentially Partial Replica) with a main screen. I want to set up the command buttons on the main form to check the Windows Logon of the user's computer during the on click event of the command button before using this command button to open a form that would only be viewed by certain users. I would store the user's IDs in a table in the database and would therefore be able to grant access to these users by adding their Windows Logon to that table.

I know that Access Security is the better way to perform what I am asking, but this will be distributed to numerous users across the network, and I just don't know how to handle this with regard to the security database that is created and I think has to be on all of the user's computers. I will not have admin access to the network so therefore think I have to avoid using the built in Security feature of Access.

Any thoughts would be appreciated. I have also considered a form based user ID and password that would segregate the users into two groups, one with access and one without. This may even be an easier option, as I could direct the group without access directly to the only form they would be able to utilize.

Thanks in advance for any assistance.

Hi to all Access Gurus - I'd appreciate comments/opinions/options on the following problem.
MS Access 2000 security of replicated database problem.

Working Scenario:-
Main DB on network server (Novell 5), accessed from workstation (W2K) and password protected.
DB is relatively small i.e. about 8 tables and 500 records but information is confidential.
Requirement is to have up to 3-users using laptops to obtain and update data off-site.
Preferred method is to replicate DB to each of laptops, synchronizing when leaving site and on return (usually 1 but not more than 2-3 days).
Although each replica on leaving site has an up-to-date copy, it is highly unlikely (although possible) that the same record(s) would be updated on different replicas and/or the Master.

Passwords can

I want to be able to synchronize 2 data databases using JRO
I would like to be able to do this using a small utility database that is NOT
linked to either of the masters.
Due to the nature of the beast it is not viable to get this done by the wizard because
the conflict rules are set, and we want it eventually to run as schedule at night.

I have made a start, by logging database and data paths in a local table in the synchronizer database.
The two replicas to be synchronized comprise
1 Replica Master (held on the initiating site
2. Replica child on the remote site (WAN)

I want to use Indirect replication.

The code below is a first attempt, but I am floored by the error message that occurs at the line where the replica is connected

Error 3709 - The connection cannot be used to perform this operation. It is either closed or invalid in this context.

Any help much appreciated. Maybe I am barking up the wrong tree.

CODE (so far).............................................. ........................................attached.. .......

We are having some problems when we close a database that it is creating another replica of this database. Is there a user setting in access that needs to be changed to stop this? Please explain....
THANKS in advance

I am using ACCESS 97 with SR2 installed.
I also have ACCESS 2000 installed as well
I have the Partial Replica Wizard installed and it does work on simple databases.
I have a problem when I try to use the Partial Replcation Wizard on a more complex database that is about 6.5 mb in size.
I have been careful to enforce integrity on the relationships to the table that contains the filter information. When I try to create the replica it gets the structure done but fails to populate the tables. I get an error reporting a problem with MSREPL35.DLL and a stack flow problem.

I would be most grateful for any help with this problem

I've inherited a database that's used primarily at another location. The users have local copies of the database that evidently stay updated--but I'm not sure how. I've tried finding the Design Master that drives all the changes but I've had no luck. I looked at one of these local copies, but clicking on Tools > Replication showed only Create Replica, and not Synchronize Now like I expected. I know there's something called Microsoft Replication Manager, but I can't find that either.

Does anyone know where I might find the replication logic and settings for this database?


Hi, all!
I am looking to run a database (replicas) on two remote networks, and synchronize them daily.
the reason i want to use replicas is because i have daily update of forms, reports ect.
The "Help" of access shows me that the solution is "internet synchronization" which can be done with replica manager thats available through Microsoft Office Developer (MOD).
My questions are as followws:
1. My understanding of "Internet synchronization" is that all replicas synchronize "into" a replica on an ftp server or something like that. am i right?
2. Is this the best solotion?
I will be very appreciative if i can get some advice.

HELP!! Have a database at work set up by someone else with a design master and 3 replicas. My Access knowledge is that of "baby designer" in that I can design applications, but am still getting to grips with programming. 3 Outworkers synchronise from p.c.s at home to 3 replicas on zip drives which are then uploaded and synchronised via an integral zip drive onto main p.c. on site. They have had problems since database designed 2 years ago, but now problems getting really bad. Both design master and replicas full of outdated information and database size is large. I have little experience of synchronised databases, but my feeling is that this method of synchronisation is inherantly insecure, and that, if we have to continue to run it, new replicas might be required. Can anyone give me some pointers urgently on what I should know before I start?? Where do I start??

What is the best strategy for upgrading an Access 97 replica set to Access 2000? I am inclined to take a replica that I know is just right, place it in a new directory, open it in Access 2000 to convert it, then turn it into a new design master using the 'Recover Design Master' menu command . I have tried this, and it seems to work, but when I create replicas from this design master, and try to synchronise them, they remember the history of the 97 replica set and offer the 97 version of the design master as the first option when selecting which database to synchronise with. The new design master does not appear until way down the list.

Am I doing things in the right order? If so, can I wipe the history of the pre 2000 replica set and start again?


I'm trying to create a partial replica from a full replica using the code below which I've put in a standard module being part of the full replica mdb.

Public Sub adhCreatePartialReplicaExample( _
strPartial As String)
' Creates a new partial replica from
' the current replica
' and populates the new partial replica.
' From Access 2000 Developer's Handbook, Volume II
' by Litwin, Getz, Gilbert. (Sybex)
' Copyright 1999. All Rights Reserved.

Dim rplPartial As JRO.Replica
Dim rplFull As JRO.Replica
Dim strConnect As String
Dim strCustOrderRel As String
Dim strOrderOrderDetailRel As String

Set rplFull = New JRO.Replica
Set rplPartial = New JRO.Replica

' Set the ActiveConnection to the full replica
Set rplFull.ActiveConnection = CurrentProject.Connection

' Step 1: Create the empty partial replica
rplFull.CreateReplica ReplicaName:=strPartial, _
Description:="Partial replica", _
Set rplFull = Nothing
Debug.Print "Partial replica created."

strConnect = _
"Provider=Microsoft.Jet.OLEDB.4.0;" & _
"Data Source =" & strPartial & ";"

' The PopulatePartial method requires an
' exclusive connection to the partial replica
rplPartial.ActiveConnection = strConnect & _
"Mode=Share Exclusive"

rplPartial.Filters.Append "fermi", _
jrFilterTypeTable, True
rplPartial.Filters.Append "g1maz", _
jrFilterTypeTable, True
rplPartial.Filters.Append "g2maz", _
jrFilterTypeTable, True
rplPartial.Filters.Append "g3maz", _
jrFilterTypeTable, True
rplPartial.Filters.Append "g4maz", _
jrFilterTypeTable, True
rplPartial.Filters.Append "IDR_POT", _
jrFilterTypeTable, True
rplPartial.Filters.Append "MazG1K", _
jrFilterTypeTable, True
rplPartial.Filters.Append "MazG2K", _
jrFilterTypeTable, True
rplPartial.Filters.Append "MazG3K", _
jrFilterTypeTable, True
rplPartial.Filters.Append "MazG4K", _
jrFilterTypeTable, True
rplPartial.Filters.Append "tblsettings", _
jrFilterTypeTable, True
rplPartial.Filters.Append "PortDez23", _
jrFilterTypeTable, True
rplPartial.Filters.Append "PortMazz", _
jrFilterTypeTable, True

' Step 2: Populate partial replica
rplPartial.PopulatePartial CurrentProject.FullName
Debug.Print "Partial replica populated."

Set rplPartial = Nothing
End Sub

The code runs to completion but I can't see the partial replica that's supposed to have been created anywhere on the hard disk.
I launch the above sub by typing
adhCreatePartialReplicaExample "scalve_bx.mdb"
in the immediate window and I guess I ought to find the partial replica named scalve_bx.mdb in the same folder where the full replica is but nothing shows up.
One thing I don't understand is how the Data Source and the ReplicaName can be the same in the code above and even stranger is the fact that if I launch the sub once more I get a run-time error saying the database already exists.

Here I am again with the same darn problem-- yesterday, in the middle of the Christmas project; the replica failed. We had had several "warnings" if you will. For the last week, for no reason the data base would lock up saying the the database was being used by another user and locked against changes. Then, yesterday it refused to sync with the other copies and when I finally decided to compact and repair to try to fix things-- it lost all the work for the day--but was able to recover about half with an append query-- I understand why only half appended but have no clue about why this all happened to begin with and am VERY worried about losing everything in the middle of the project-- almost 2000 children would not get gifts for Christmas. If anyone has a good idea to save this--or keep it stable until Christmas and then would really appreciate input on better ways to handle the whole datakeeping process for the center.

I had my Access 97 Design Master on a laptop whose hardrive irretrievably went into the next parallel dimension. I've since installed 2000 on the Win98 box where the replica lives, and it's warning me that conversion of the replica will destroy all the forms and reports (I tried it on one database and it really did!). I confess I had willy-nilly strewn numerous replicas about, and there seems no way to synchronize and make the current replica a design master. Any bright ideas for getting out of this one?