Re: Access 2003 code corruption problems

"James Beswick" <jamesbeswick@xxxxxxxxx> wrote in
news:1124297063.806069.260790@xxxxxxxxxxxxxxxxxxxxxxxxxxxx:

> I think you should have a little more respect for the writers in
> this thread. I've been working with Access for over ten years and
> I can tell you that 2003 has some strange code corruption problems
> that were not in Access 97. And don't call the guy lazy - I'm sure
> he knows what he's doing too. Let's keep polite on these boards,
> please.

There was far too insufficient evidence adduced on the subject of
code corruption in A2K3 to justify the ridiculous remarks about
switching to .NET, as well as the off-the-wall blanket criticisms of
Microsoft.

I'm no fan of Microsoft, but I think it's best to not waste time
levelling charges at them that are undeserved.

--
David W. Fenton http://www.bway.net/~dfenton
dfenton at bway dot net http://www.bway.net/~dfassoc
.

Relevant Pages

  • Re: NIC settings for SQL 2005 and windows 2003?
    ... I appreciate your defense of technical writers, but they are just that, ... The people I know who write for Microsoft are actually very ... with SQL Server 2005: ... Maximize data throughput for network applications (the option that ...
    (microsoft.public.sqlserver.connect)
  • Re: Mad At Microsoft (Security)
    ... Microsoft software was written at a time when the ... writers took it and found holes in the software. ... Then virus writers found other ...
    (microsoft.public.security)
  • Re: Worm spoofs Google on infected PCs
    ... the writers have some financial interest in Microsoft or yahoo? ...
    (alt.computer.security)
Loading