Stuart McLachlan
stuart at lexacorp.com.pg
Sun Oct 13 18:16:23 CDT 2013
Or Sharepoint. On 13 Oct 2013 at 16:07, Charlotte Foust wrote: > Because they want you to use SQL Server if you need replication. > > Charlotte > > > On Sat, Oct 12, 2013 at 10:12 AM, Doug Murphy <dw-murphy at cox.net> > wrote: > > > Hi Jim, > > > > Thanks for your thoughts. There should be no difference when > > updating mdb file in 2007 or 2010, the file is still in 2000 - 2003 > > mdb format. BUT there does seem to be a difference. I just verified > > that I can edit the client file in 2007. I found that one of the > > servers still has 2007 installed. Just remoted in and updated an > > existing table. > > > > Very slow process as this is an old server, but it does work. Why > > does MS feel they have to screw up useful, working features and then > > add a bunch of APP/Web stuff that really isn't appropriate for what > > Access is good at? Really P.O-ed. > > > > Doug > > > > -----Original Message----- > > From: accessd-bounces at databaseadvisors.com > > [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Jim > > Lawrence Sent: Saturday, October 12, 2013 9:55 AM To: Access > > Developers discussion and problem solving Subject: Re: [AccessD] > > Modifying Replicated Database Using Access 2010 > > > > No wonder. > > > > The tech your using is truly on some edge. It many be difficult to > > track down the ten other people who have used it recently. I feel > > your pain...been there doing it but with some other ancient tech. > > > > Maybe you can make the changes in 2007 and just upgrade the results > > to 2010. It appears, the old replication code still exists in 2010 > > but the IDE has been crippled or just neglected to point where it no > > longer functions. > > > > Jim > > > > ----- Original Message ----- > > From: "Doug Murphy" <dw-murphy at cox.net> > > To: "Access Developers discussion and problem solving" > > <accessd at databaseadvisors.com> > > Sent: Saturday, October 12, 2013 9:34:37 AM > > Subject: [AccessD] Modifying Replicated Database Using Access 2010 > > > > Folks, > > > > I know there are some old timers on this list who have worked with > > Access Jet Replication. Not to many folks use or even know about > > replication any more since it was depreciated starting with the > > advent of the accdb file format. In any case I use it where networks > > are slow or unreliable and it just works. That is until I tried to > > maintain an replication system using Access 2010. > > > > We have a system that uses replication to allow folks in two > > different locations to work with a common database back end. The > > network is not high quality, and slow so I used replication to put a > > back end at each location and keep them synchronized. > > Synchronization is done through the Replication Manager and > > synchronizer running on a schedule. This has been working great for > > the past two years. The system was originally developed and used > > with Access 2007 but with the back end in mdb format. So now the > > client is up to Access 2010. The client wanted some changes to the > > back end, entailing some new tables and new fields added to existing > > tables. No problem I think. I went to the site and opened the > > Replica set design master using Access 2010 and added the new tables > > with no problem. Then I tried to add the new fields to existing > > tables. I could do that in design view but when I tried to save the > > changes I get a message 'Operation not supported for this type of > > object' message. I banged my head against the wall for a while > > thinking I was doing something wrong, then gave up working at the > > client facility. I did run the synchronizer before leaving and the > > new tables propagated properly to the other managed databases. This > > part is working. > > > > After returning to my office I thought possibly this is an Access > > 2010 issue. I fired up a virtual machine with Access 2007 on it and > > a running replication system of the same database. In Access 2007 I > > could open the design master and add fields to existing tables with > > no errors and the changes would save. Is this an Access 2010 issue > > or is there something else going on? I'd hate to have to re-install > > Access 2007 on one of the client computers to make these changes. I > > have the same system running on my Access 2010 machine and I can > > duplicate the 'Operation not supported for this type of object' > > issue using Access 2010 in my office. Any thoughts? > > > > Thanks in advance for your assistance. > > > > Doug > > > > PS. Tried this question on UtterAccess with no reponse. > > > > -- > > AccessD mailing list > > AccessD at databaseadvisors.com > > http://databaseadvisors.com/mailman/listinfo/accessd > > Website: http://www.databaseadvisors.com > > -- > > AccessD mailing list > > AccessD at databaseadvisors.com > > http://databaseadvisors.com/mailman/listinfo/accessd > > Website: http://www.databaseadvisors.com > > > > -- > > AccessD mailing list > > AccessD at databaseadvisors.com > > http://databaseadvisors.com/mailman/listinfo/accessd > > Website: http://www.databaseadvisors.com > > > -- > AccessD mailing list > AccessD at databaseadvisors.com > http://databaseadvisors.com/mailman/listinfo/accessd > Website: http://www.databaseadvisors.com >