Moving to client/server

Hi
I have an access mdb frontend/backend app. To use sql server as backend, is
it better to keep the mdb frontend or should I switch to adp instead?
Thanks
Regards
Hi,
That does not matter. All depends up on your requirement.
Thanks
Hari
SQL Server MVP
"John" <John@.nospam.infovis.co.uk> wrote in message
news:e0AGovclFHA.2484@.TK2MSFTNGP15.phx.gbl...
> Hi
> I have an access mdb frontend/backend app. To use sql server as backend,
> is it better to keep the mdb frontend or should I switch to adp instead?
> Thanks
> Regards
>
|||What is the criteria to choose one over the other?
Regards
"Hari Prasad" <hari_prasad_k@.hotmail.com> wrote in message
news:%23$GQX$dlFHA.3316@.TK2MSFTNGP14.phx.gbl...
> Hi,
> That does not matter. All depends up on your requirement.
> Thanks
> Hari
> SQL Server MVP
> "John" <John@.nospam.infovis.co.uk> wrote in message
> news:e0AGovclFHA.2484@.TK2MSFTNGP15.phx.gbl...
>
|||Per John:
>What is the criteria to choose one over the other?
If you've got an Access UI that works, I can't think of any reason to migrate to
another platform unless performance goes down the tubes when the DB is migrated
and somehow the other platform can remedy that. OTOH, keeping the same UI and
feeding with with stored procedures would probably accomplish anything that
another tool could.
PeteCresswell
|||On Sun, 31 Jul 2005 13:23:35 -0700, "(PeteCresswell)" <x@.y.z.invalid> wrote:

>Per John:
>If you've got an Access UI that works, I can't think of any reason to migrate to
>another platform unless performance goes down the tubes when the DB is migrated
>and somehow the other platform can remedy that. OTOH, keeping the same UI and
>feeding with with stored procedures would probably accomplish anything that
>another tool could.
Even switching to stored procedures is a huge job that means re-engineering
all the editable bound forms, and it's usually not necessary.
Converting queries to views and/or stored procedured is a good idea when...
1. A particular Access query can't be convinced to optimize well using linked
tables.
2. There will be multiple front-ends and you want to move much of the business
logic to the server, so it can be managed in one place without changing
multiple applications. Note that if you have SQL Server 2000 or newer, you
can often do this with Views and Instead Of triggers rather than stored
procedures, which is a much more Access-friendly way of doing it.
|||You can keep access itself as frontend
"John" wrote:

> Hi
> I have an access mdb frontend/backend app. To use sql server as backend, is
> it better to keep the mdb frontend or should I switch to adp instead?
> Thanks
> Regards
>
>

Moving my SQL Server to another computer

I will moving my SQL Server to another server. The plan is to stop SQL Server copy database file to a temp netwokr location, Switch off this server. Configure the new server with the same name and IP, install SQL to the same paths and service pack to the same level (SQL 2000 sp3). Then start and stop the SQL server. Once stop I will then copy the old database file over the new ones.

I know in general this works as I have doen this many times before expect this time round there is a replicaiton database which is new, I am expecting this will work the same but has any one else tried this before?

Unfortunately, you have to disable the publication before you can detach and move the database.

BTW, I recommend you to detach the database before you move the database file to another server, this ensure you can attach it to the new server even though it is missing the transaction log file.