Home | Contact Us | FAQ | Search & Site Map | Link to Us
Sign In | Join | Other 45 Sites in Network
Home
Discussion GroupsFormsForms ProgrammingQueriesModules / DAO / VBAReports / PrintingMacrosDatabase DesignSecurityConversionImporting / LinkingSQL Server / ADPMultiuser / NetworkingReplicationSetup / ConfigurationDeveloper ToolkitsActiveX ControlsNew UsersGeneral 1General 2
Access DirectoryToolsTutorialsUser Groups
Related Topics
SQL ServerOther DB ProductsMS OfficeMore Topics ...

MS Access Forum / Replication / April 2008

Tip: Looking for answers? Try searching our database.

URGENT - change retention period ?

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
info27 - 24 Apr 2008 22:38 GMT
Hello,

In Sept. 2005 I changed the retention period of my access-DB (Access 2000-DB
in Office 2003) by using JRO:

------------------------------------------------------------------------------
---------------------------
In the Design Master, set a reference to "Microsoft Jet and Replication
Objects 2.x Library". Then use the following code:

  Dim oReplica As JRO.Replica
  Set oReplica = New JRO.Replica

  oReplica.ActiveConnection = CurrentProject.Connection
  oReplica.RetentionPeriod = 1000 'Days

  Set oReplica = Nothing

Then synchronise all the replicas so the new value filters through the set.
------------------------------------------------------------------------------
----------------------------

Now the 1000 Days are over ...
I tried today to change the retention period by using the JRO-method as
described above.
Now (1000 days later) It doesn't work - I got the following error message:´

runtimeError: -2147024770 (8007007e)
method 'Connection' for the object '_CurrentProject' has failed

Has anybody an idea? What´s the problem?

Thanks Chris
David W. Fenton - 25 Apr 2008 03:27 GMT
> Now the 1000 Days are over ...
> I tried today to change the retention period by using the
> JRO-method as described above.

Once the retention period expires without a synch, the replica is
done -- there is no way to recover it so that it can be a
synchronizable replica again.

Signature

David W. Fenton                  http://www.dfenton.com/
usenet at dfenton dot com    http://www.dfenton.com/DFA/

info27 - 25 Apr 2008 08:16 GMT
>> Now the 1000 Days are over ...
>> I tried today to change the retention period by using the
[quoted text clipped - 3 lines]
>done -- there is no way to recover it so that it can be a
>synchronizable replica again.

Hi David,

Thanks for your answer.
(you gave me already some help already Sept 29th 2005)

Detail information about my DB:
1. developed in A97 (started in year 1998)
2. converted in A2000 --> working with replication

10 years later - This is now my configuration (since 2005):
3. Changing to a Terminalserver-Environment  (Terminalserver 2003/Access 2003
in Access 2000 Mode)
Therefore I use the Designmaster on Terminalserver - splitted in BE+FEs (14
FEs) -
as recommended in some postings on accessmonster.com. This works great! I
have no other replicas which are generated with replication manager (only the
FEs which are copy from Designmaster-FE)!!
That means I don´t work with replication an I need not to synchronize.

(INFO: great advantage of using the Designmaster is that user of the FEs
can´t make changes in forms, reports an so on).

The problem since yesterday is that every time  you start the DB (FE) the
message ("must synchronize the replicat within xx days / can`t synchronize
the replicat ......) is displayed; it`s
not really funny for the 14 users.

I had this problem already in the year 2005. 2005 I changed the retention
period (from 60 to 1000) as described in my posting (now 994 days are over);
but now it isn´t possible to change the retention period.

That means I only need a possibility to change the retention period in
Designmaster, then no message appears and all users are lucky

I hope you understand my problem ...

Thank you
Chris
David W. Fenton - 26 Apr 2008 00:10 GMT
"info27 via AccessMonster.com" <u11672@uwe> wrote in news:8331e7579ae75
@uwe:

> I hope you understand my problem ...

The problem is that you're replicating front ends. You shouldn't do
that, as Jet replication really only works well for back ends.

If you don't want your users to make changes, then make your front ends
MDEs.

Signature

David W. Fenton                  http://www.dfenton.com/
usenet at dfenton dot com    http://www.dfenton.com/DFA/

info27 - 26 Apr 2008 13:42 GMT
>"info27 via AccessMonster.com" <u11672@uwe> wrote in news:8331e7579ae75
>@uwe:
[quoted text clipped - 6 lines]
>If you don't want your users to make changes, then make your front ends
>MDEs.

Hello,

Thanks for helping ...

It works.

Best regards
Chris

Rate this thread:






 
Sign In
Join
My Latest Posts
My Monitored Threads
My Blog
My Photo Gallery
My Profile
My Homepage

Start New Thread
Enable EMail Alerts
Rate this Thread



©2008 Advenet LLC   Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.