MSDE replacing Access2000 in VB Application

I support a Visual Basic application, about 150,000 lines. It's basic
functionality is to pull data from an Oracle database and store it in arrays,
then perform about 6 dozen different kinds of analysis on the data, as the
user chooses.
Access 2000 is used in two fashions, both behind the scenes and static. (1)
The data from Oracle is temporarily stored in one MDB for cross-tabbing and
reorganization into the VB arrays. (2) Certain reference databases are
populated in other MDB files in order to support off-line analysis. Also,
user-defined associations are stored in a separate MDB.
So here are the questions: would I benefit from the use of MSDE? If not, why
not (to explain to boss and customer). If yes, how, and with what kind of
effort?
Thanks!
If you're making heavy use of cross-tab queries, that's probably
reason enough right there to stick with Access mdb's. It's much harder
to do in SQL Server, and you'd need to rewrite that entire piece of
your application. It doesn't appear that there are really any
advantages to using MSDE in your case since you also require
heterogeneous queries to Oracle, which is also much easier from
Access. It works differently in SQL Server, and you'd need to rewrite
a lot of your data access functionality as well. I can't really think
of any benefit to migrating this particular app to MSDE unless you're
getting paid by the hour :-)
-- Mary
On Tue, 14 Sep 2004 10:03:03 -0700, Rick Coen
<rick.coen@.eds.com.nospam> wrote:

>I support a Visual Basic application, about 150,000 lines. It's basic
>functionality is to pull data from an Oracle database and store it in arrays,
>then perform about 6 dozen different kinds of analysis on the data, as the
>user chooses.
>Access 2000 is used in two fashions, both behind the scenes and static. (1)
>The data from Oracle is temporarily stored in one MDB for cross-tabbing and
>reorganization into the VB arrays. (2) Certain reference databases are
>populated in other MDB files in order to support off-line analysis. Also,
>user-defined associations are stored in a separate MDB.
>So here are the questions: would I benefit from the use of MSDE? If not, why
>not (to explain to boss and customer). If yes, how, and with what kind of
>effort?
>Thanks!
|||I agree with Mary but wanted to point out that the next version of MSDE (Sql
server 2005 express) is supposed to support the cross tab queries (PIVOT I
think)
"Mary Chipman" <mchip@.online.microsoft.com> wrote in message
news:g4fek0lnib00ce9nimo5urm9jb2vssgn5n@.4ax.com... [vbcol=seagreen]
> If you're making heavy use of cross-tab queries, that's probably
> reason enough right there to stick with Access mdb's. It's much harder
> to do in SQL Server, and you'd need to rewrite that entire piece of
> your application. It doesn't appear that there are really any
> advantages to using MSDE in your case since you also require
> heterogeneous queries to Oracle, which is also much easier from
> Access. It works differently in SQL Server, and you'd need to rewrite
> a lot of your data access functionality as well. I can't really think
> of any benefit to migrating this particular app to MSDE unless you're
> getting paid by the hour :-)
> -- Mary
> On Tue, 14 Sep 2004 10:03:03 -0700, Rick Coen
> <rick.coen@.eds.com.nospam> wrote:
arrays,[vbcol=seagreen]
the[vbcol=seagreen]
(1)[vbcol=seagreen]
and[vbcol=seagreen]
Also,[vbcol=seagreen]
why[vbcol=seagreen]
of
>