Re: Access 2000 - Realtime Development - Should i stick with Access97

From: Jado (ploxly_at_hotmail.com)
Date: 06/23/04


Date: Wed, 23 Jun 2004 11:37:42 +0100

Thanks Allen

I'll be sticking with Access 97

just one last thing though...

if I needed to start using SQL Server to store Tables of an Access 97 front
end, would this force the need to upgrade.

if not, are there many major benefits of using A2000 appose to A97 in
conjunction with SQL Server 2000

I'll let you go now :)

Your comments have proved invaluable in helping me make the right decision

Many Thanks

Jado

"Allen Browne" <AllenBrowne@SeeSig.Invalid> wrote in message
news:elcFEU$VEHA.1888@TK2MSFTNGP11.phx.gbl...
> Comments interspersed.
>
> --
> Allen Browne - Microsoft MVP. Perth, Western Australia.
> Tips for Access users - http://allenbrowne.com/tips.html
> Reply to group, rather than allenbrowne at mvps dot org.
>
> "Jado" <ploxly@hotmail.com> wrote in message
> news:O$lp5i6VEHA.1164@tk2msftngp13.phx.gbl...
> >
> > > The problem you refer to is the monolithic save. [snip]
> >
> > do you mean 2 developers working in design view?? (I would be the only
one
> > needing to access objects in design view)?
>
> If any other user is *using* (not only if they are designing) any form or
> report in the database, you will have problems saving in A2000 and later.
>
> > out of interest, after reading about all those possible problems, would
> you
> > mind telling me, in your opinion, the main benefits an upgrade from
Access
> > 97 to 2000 would bring.
> >
> > I've read about the new features of A2000, but as I've never dabbled, I
> > wouldn't know which features have proved to be well worth while, and
which
> > were a waste of time!
>
> If you store your data in Access tables, the only new, useful feature that
> works without problems is that Forms have an undo event.
>
> AutoCorrect causes more problems than it solves.
> Conditional Formatting is a nice idea, but buggy.
> The new field types do not work correctly.
> The new relationship types are not supported in the interface.
> You have to reset problem properties every time you create a table, text
> field, for form.
> Many of the bugs have been present for 4 years, and are not being fixed.
>
> So why upgrade? If you are working with JET/Access tables, they only
reason
> is because you have support clients who are using later versions.
>
>



Relevant Pages

  • Re: Newbie help
    ... think I can probably get what I need using SQL Server (the ... > To efficiently store and retrieve data for your needs, ... You only store changed values (as ...
    (microsoft.public.sqlserver.programming)
  • Re: meta data & full text search
    ... There are more issues (transaction control, change control, audit of ... storing the files in a SQL Server table's column defined with an IMAGE ... if you store the files ... consistency of the database, indices, backup, restore, etc. ...
    (microsoft.public.sqlserver.fulltext)
  • Re: Connecting remotely through VPN
    ... Reason: Your upgrade is blocked. ... Requirements" topics in SQL Server 2005 Setup Help or SQL Server 2005 Books ... information about edition upgrades, see the Version and Edition Upgrades ... I think that your SQL Browser Service did not work well. ...
    (microsoft.public.sqlserver.connect)
  • Re: SQL 2005 wont upgrade using R2 discs
    ... But when I try and upgrade the default instance I still get this error: ... Microsoft SQL Server 2005 Tools ... I uninstalled the SQL 2000 version and it let me install ... information about edition upgrades, ...
    (microsoft.public.windows.server.sbs)
  • Re: Creating a new Access database file (.mdb) in .NET/C#
    ... You definitely need to download my Ebook. ... It can be passed around as a file like JET and backed up in a similar fashion. ... Consider that this database is also fully encryptable--a feature not in JET or in SQL Server until 2008. ... Per the MS product pages, I'm eligible for the Upgrade package, and ...
    (microsoft.public.dotnet.framework.adonet)