19. maj 2004 - 15:14Der er
5 kommentarer og 1 løsning
Hvordan Styres replikering via kode i Access XP
En større datamængde skal deles mellem flere afdelinger adskilt af et WAN. Desuden arbejder nogle hjemme på en 2 mbit ADSL. Hastigheden er derfor ikke forbavsende store.
Førend at jeg kaster mig over en migrering til SQL, vil jeg forsøge om replikering af data en brugbar løsning.
Meget lidt står der om replikering i access xp på nettet, men meget har sikkert ikke ændret sig.
Spørgsmålet er, om der en nem måde at tilgå replikering på for en standardbruger i.e trk på en kap på en formular. Jeg søger derfor noget kodeværk, som kan styre denne replikering frem o g tilbage. Et af problemer er, at replikererde data godt kan flyttes ned på et tilfældig drev. Masterbase kan ikke se replika på c drevet hjemme men hjemmedrevet kan se master på T drevet på server.
Hvor finder jeg som sagtr kode til at styre replikering og er der pitfalls.
hnteknik>I must admit that I dont think replication is used so much, certainly not in Access. There are a couple of white papers you can download which may help.
Jeg sidder med det samme problem, men har opgivet det.
Jeg tror ikke at det kan betale sig at bruge ret mange kræfter på at løse det, for i løbet af kort tid bliver hastigheden på WAN forbindelserne vel så stor, at problemet er løst ad den vej.
A number of years back I learnt a bit about replication, and one thing I remember was that it is necessary to have replication in mind BEFORE the database is made. Replication converts autonumbers to GUIDS and this can have consequences of relationships and other things. But I'm sure the white papers mention this too. SQL Server could also help speed things up.
terry> I don't know, what happened. I had a long text as a comment, but it all ended up into nothing. Whats up with this site at the moment. Your links are old ( and outdated DAO) stuff and I knew of them allready. I have to consult my old friend Garry from downunder (vb123.com) before dropping it, but to me it already stinks like a dead herring. BTW as clinet being one of the larger tele/ISP, I don't think the WAN can be much more effective but they are testing. I think they are running VPN from homeoffice. The problem is tens of thousands of records in more than one table have to be transported over the wan. SQL is the solution I know or maybe internet.
I have a Cisco VPN connection to work and my Internet connection is only 1Mb (at best). This means that all processing is done on the server and I just see the result. The performance in very good. Going over to SQL Server should help as you only get the records you ask for, but if your dB doesnt take this into account then you will still end up having to drag everything over the WAN.
Anyway, thanks for the points. hope you find a solution!
P.S Eksperten seem to have many problems at the moment, if it continues then I think I'll be gone.
Synes godt om
Ny brugerNybegynder
Din løsning...
Tilladte BB-code-tags: [b]fed[/b] [i]kursiv[/i] [u]understreget[/u] Web- og emailadresser omdannes automatisk til links. Der sættes "nofollow" på alle links.
