[AccessD] SQL vs Access

MDB will do fine, using ODBC. Simplest approach is to create identical
setups on your home network. I do this all the time by creating a directory
on a server then mapping to it from my development box, calling it whatever
I need to mirror the client's setup.

A.

On Fri, Feb 1, 2008 at 1:20 PM, Rocky Smolin at Beach Access Software <
rockysmolin at bchacc.com> wrote:

> Does an A2K3 front end app linked to a SQL back end need to be an ADP or
> just a regular mdb?
>
> Rocky
>
>
>
>
>
>
>
>
> -----Original Message-----
> From: accessd-bounces at databaseadvisors.com
> [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of David Emerson
> Sent: Friday, February 01, 2008 9:56 AM
> To: Access Developers discussion and problem solving
> Subject: Re: [AccessD] SQL vs Access
>
> I have a similar project being considered.
>
> I have done a few projects with AccessXP ADP and SQL2K.  Is there a
> free/lite version of SQL2K?  If so, will a database created in SQL2K work
> seamlessly in the lite version?
>
> If there is not, I also have SQL2005.  Will a database created in this be
> able to be used seamlessly with SQL Express.
>
> Can AccessXP ADP's work with SQL2005?
>
> Regards
>
> David Emerson
> Dalyn Software Ltd
> Wellington, New Zealand
>
> At 2/02/2008, you wrote:
> >Rocky,
> >
> >As Susan wrote, SQL Express is a viable option. The IT department's
> >point about backup and restore is well-taken, too. Since they already
> >have a backup strategy in place, adding one more DB to it should be
> >trivial. Then you (and they) can forget about it, except for the
> >verification step, which they probably have automated already for their
> other databases.
> >
> >Were I you, I would acquiesce immediately on this one. You have nothing
> >to lose but credibility if you fight them, and an opportunity to work
> >with SQL Express or SQL Server.
> >
> >Given this path, you should be concerned about which version and format
> >you'll be using. IMO the best combination is A2K or A2K3 using ADP
> >format to talk to a SQL 2000 db. If you try talking to a SQL 2005 db
> >from either of those Access versions, it works, sort of, but you miss a
> >lot of the goodies due to the internal restructuring of the SQL db
> >format. OTOH if you're going to use A2K7 then it's a good fit with SQL
> 2005.
> >
> >hth,
> >Arthur
> >
> >On Fri, Feb 1, 2008 at 12:03 PM, Susan Harkins <ssharkins at gmail.com>
> wrote:
> >
> > > You might find SQL Server Express easier to work with than Access --
> > > they might be willing to make that compromise with you.
> > >
> > > Susan  H.
> > >
> > >
> > > > Hi Rocky
> > > >
> > > > As he has several running servers and a proven backup scheme, he
> > > > has a valid point.
>
> --
> AccessD mailing list
> AccessD at databaseadvisors.com
> http://databaseadvisors.com/mailman/listinfo/accessd
> Website: http://www.databaseadvisors.com
>
> No virus found in this incoming message.
> Checked by AVG Free Edition.
> Version: 7.5.516 / Virus Database: 269.19.18/1254 - Release Date:
> 1/31/2008
> 8:30 PM
>
>
> --
> AccessD mailing list
> AccessD at databaseadvisors.com
> http://databaseadvisors.com/mailman/listinfo/accessd
> Website: http://www.databaseadvisors.com
>