ADP does not contain data. It is pure frnt end application, connected to SQL Server, with all data sit in SQL Server database (while *.mdb front end can hold data on its local table). Using ADP in your situation does not help at all, or not much different from using *.mdb linked tables.
<christopher.b.lewis[ at ]gmail.com> wrote in message news:1154622085.921249.242150[ at ]75g2000cwc.googlegroups.com...
[Quoted Text] >I have been using Access for many years. I now need to upsize to SQL > because my website is getting much more traffic than it used to. I > want to continue using my existing Access forms to populate the new SQL > database. > > I have tried to link my existing local Access forms to my remote SQL > sever database. However, my forms have many lookups that pull > thousands of rows of data; so performance is inadequate. > > I was thinking that a quick and good solution would be to update my > data locally using an Access Database Project (the lookups should > perform reasonably well locally) and then push the new data updates to > the live, remote SQL database. > > Does this sound like a fine way to work? > Any suggestions on how I should push my new data to the remote SQL > server? (I have never done this before.) What concepts/processes > should I learn about to get this done? Any specific recommendations on > how to begin would be much appreciated. > > One of my concerns is that during the data transfer from local to > remote, the integrity of the relationships will break. Is there a > standard way of dealing with that? >
|