Re: Converting an Access Application

From: Joe Fallon (jfallon1_at_nospamtwcny.rr.com)
Date: 04/28/04 

Date: Wed, 28 Apr 2004 14:09:49 -0400

Very good points.
Up until the last one!

LOL! 

-- 
Joe Fallon
"Bonj" <a@b.com> wrote in message
news:eTtqUuULEHA.556@TK2MSFTNGP10.phx.gbl...
> The bad news is that you are going to have to face the fact that you
*will*
> have to rewrite it if you want to eliminate Access as it gets more and
more
> stretched - which from what you've said, means you will have to rewrite
it.
> The good news is that "re-writing" something in another language means
just
> that - re*writing* it. It doesn't mean re-researching application layout,
> nor re-analyzing requirements, nor does it mean re-figuring-out
algorithms -
> you can take consolation in the fact that you don't have to go through the
> same amount of work again to achieve the same-thing-only-different. Class
> structure, control of flow design and possibly even tangible things such
as
> any ocxs / dlls there might be, can be kept.
> You can optimize more aswell, by using SqlConnections which bypass OLEDB
if
> you're using SQL server like you say, the best approach is to use these
> specific SQL server connections and use stored procedures for ALL data
> access (it may sound hard at first but there's very few applications that
> can't eliminate the need for dynamic SQL).
> Given that you've already got this lot figured out, it would be a better
> than average opportunity to learn .NET, if you don't already know it - or
> more of it if you do. But use C# not VB.NET - VB.NET's just ...well,
> *wrong*.
>
> "Randy" <randy@NoSpamForMe.com> wrote in message
> news:108vkad6dm0gs11@corp.supernews.com...
> > Hi all,
> >
> > Not sure if this is feasible or not, but I'm gonna ask anyway.
> >
> > My company has developed an application using MS Access 2k as a front
end
> to
> > SQL Server 2000.  As we grow, and add customers (who are also growing)
> > Access's limitations soon come to the fore front of most of our
problems.
> >
> > Is there a relatively easy way to convert from Access 2k to Vb .Net or
> even
> > VB 6 without basically re-writing the whole app?
> >
> > I am thinking there isn't, but I thought I would ask those who are
smarter
> > then I in this arena.
> >
> > Thanks In Advance (even if it is bad news)
> >
> > Randy
> >
> >
>
>

Relevant Pages

  • Re: command timeout - SQL 2005 express - critical customer down
    ... The good news is that this is fixable, the bad news is that you haven't fixed it--just patched the problem. ... Most SQL Server installations use dynamic IP assignments--each named instance gets its own dedicated port assigned when the service starts. ... It turns out that the firewall was turned on on the server so we had to ...
    (microsoft.public.dotnet.framework.adonet)
  • which is best
    ... i want to develop such a application in geo geaphical news web site with SQL ... Server replication where every country have SQL Server database in their ... 175 Country headquerters, with local news updated every miniute. ...
    (microsoft.public.sqlserver.replication)
  • Re: Converting an Access Application
    ... > The good news is that "re-writing" something in another language means ... > you're using SQL server like you say, the best approach is to use these ... > "Randy" wrote in message ... >> VB 6 without basically re-writing the whole app? ...
    (microsoft.public.vb.general.discussion)
  • Re: Converting an Access Application
    ... The bad news is that you are going to have to face the fact that you *will* ... stretched - which from what you've said, means you will have to rewrite it. ... you're using SQL server like you say, the best approach is to use these ... > VB 6 without basically re-writing the whole app? ...
    (microsoft.public.dotnet.languages.vb)
  • Re: Converting an Access Application
    ... The bad news is that you are going to have to face the fact that you *will* ... stretched - which from what you've said, means you will have to rewrite it. ... you're using SQL server like you say, the best approach is to use these ... > VB 6 without basically re-writing the whole app? ...
    (microsoft.public.vb.general.discussion)