Re: migrating from access: mdb or sql server files or what

From: Norman Yuan (nobody_at_nowhere.no)
Date: 08/17/04


Date: Tue, 17 Aug 2004 08:03:37 -0700

For a single user ans single computer, and Access installed, you already
have everything. If you could refine the code in Access further, it could be
as perfect as you can get. Why convert it to SQL Server (even the license
cost is not an issue, it need significant more knowledge to manage,
definitely not doable task for average database user, even a self-claimed
exerienced computer user), and VB. As for VB.NET, it is almost entirely
different animal, you certainly will rewrite everthing from scratch (except
for the data table), if you are to move it to .NET.

"PF" <pf@arobas.net> wrote in message
news:rjnUc.82544$sk2.1647355@wagner.videotron.net...
> Hi all,
>
> I have an access application
> code and data in the same file.
>
> It runs on a single computer
> with a single user
>
> Speed of response is critical.
>
> The program seek continuously for a
> variable string, if found, a record is created
> with the key and additional data.
> In peak time 3 rerod/second of 40 bytes.
>
> We want to migrate to vb (vb.net)
>
> The question is: for speed should
> we stay with mdb table, or should we link to
> a sql server? or any other kind?
>
> Should we install a sql server 2000
> on that computer and run the
> program in the server directly?
>
> If use we have to connect to the server
> make a request to search for a string and
> then make a request for an insert.
> I suppose this would be longer than an
> insert in a mdb table. ?
>
> We have an old oracle 8.0 database
> that came with novell and is not in use.
> Is it thinkable to use it?
>
> What is the best choice?
> a vb program with an mdb table?
> a sql server running a program?
> what kind of connection is the fastest
>
> actually we are using DAO.
> there are ADO,oledb,odbc
>
> Cans someone give me a hint?
>
> Best regards
>
> pierre
>
>



Relevant Pages

  • migrating from access: mdb or sql server files or what
    ... It runs on a single computer ... Should we install a sql server 2000 ... then make a request for an insert. ... insert in a mdb table. ...
    (microsoft.public.vb.database)
  • Re: migrating from access: mdb or sql server files or what
    ... It runs on a single computer ... Should we install a sql server 2000 ... insert in a mdb table. ... If it's a single user database and you haven't had any database corruption issues then there ...
    (microsoft.public.vb.database)
  • Re: Access / DAO - Whats the Future
    ... when the schema changes. ... Would you recommend that we change to SQL Server Express? ... (single user, no install required - just copy&paste assemblies). ... RightHand .NET consulting & development www.rthand.com ...
    (microsoft.public.dotnet.framework.adonet)
  • Re: Windows forms application and database back-up
    ... What you write is valid as it is running as multi user source, but as it is single user like the OP wrote, than in my idea simple make copies has the same effect. ... I was also going for the backup/restore, but rejected that because it has in my idea no advantages in a single user situation. ... attached to the SQL Server instance), ... The other option would be to use SQL Server Express' USER INSTANCE, to which, the user do not have to have local admin rigth to attach database to SQL Server Express instance. ...
    (microsoft.public.dotnet.general)
  • Re: Visual C# Express question
    ... > not sharable and the user can admin the thing without being admin. ... > pretty cool way to go if you just need a db for your single user app. ... >> "Easily move or copy your SQL Server Express databases to another ... >> Voodoo Programming: Things programmers do that they know shouldn't work ...
    (microsoft.public.dotnet.framework)