[AccessD] SQL vs Access

The answer is Yes, within limits. I outlined some of these in a previous
reply. There are a very few other gotchas, such as the difference in date
ranges. I'd also suggest that prior to upsizing you go through your forms
etc. and look for any record source or row source that begins with "SELECT".
If you find any, change them to saved queries before upsizing. Otherwise the
upsizer will do it for you, giving them really intuitive names like
~!)xys!~.

hth,
Arthur

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

> Arthur:
>
> I have SQL 2005 running here so I could upsize the current mdb back end
> with
> the wizard and relink the tables.  Does SQL 2005 play well with A2K3?
>
> Then, how do I send the back end to the client?  I know it doesn't move
> like
> an mdb but how is it done?
>
> Thanks to all for your input and regards,
>
> Rocky
>
>
>
>
>
>
>
>
> -----Original Message-----
> From: accessd-bounces at databaseadvisors.com
> [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Arthur Fuller
> Sent: Friday, February 01, 2008 9:14 AM
> To: Access Developers discussion and problem solving
> Subject: Re: [AccessD] SQL vs Access
>
> 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
> >
> --
> 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
>