On Jun 11, 8:16 pm, "Michael Cole" <n...@[EMAIL PROTECTED]
> wrote:
> Randy Reimers wrote:
> > (Hope I'm posting this correctly, otherwise - sorry!, don't know
> > what else to do)
> > I wrote a set of programs "many" years ago, running in a type of
> > basic, called "Thoroughbred Basic", a type of business basic. I need
to
> > re-write it, bring it kicking and screaming to run on Windows XP.
This is
> > for
> > a video rental place, tracks movie and game rentals, customers,
employee
> > transactions, reservations, does re****ts,..... and on.
> > I know some of Visual Basic - I now write VB scripts for work. Can
> > anyone help with suggestions, as to converting this to a new
> > language? What may be easiest for me? And, what type of database
> > engine would be best? SQL, Access, flat files, I don't know enough.
> > This does NOT run under Windows, Linux, or any "new" OS - but I can
> > ex****t all the files, and programs to DOS. They currently are
> > running on 20-30 286 or 386 computers - not a misprint - OLD! Not
> > networked, not neccessary.
>
> For what its worth, my approach would be: -
>
> Database first - MS Access. As they are stand alone, SQL Server or
others
> like that (Sybase, Oracle) are overkill. The other options include
stuff
> like dBase, but Access is reasonably common and easy to use, which will
make
> it easier for administration - you should be able to get some people at
> remote sites who can use it if needed.
>
> Front end - VB6 with DAO access. Again - for ease of use and upgrading
of
> existing code. Note that this does not nessesarily mean that this is
the
> best option for all, but you have existing basic code and a lot should
> upgrade. In terms of your
>
> > The data files it uses are called "Direct" and "Sort". I have about
> > 90 programs, a few are overlays, most are stand-alone, 25-30 are just
> > for re****ting purposes. It can stay character based - no need for
> > fancy screens or pix.
>
> If you use VB, then you should make it screen based rather that
character
> based, it is pretty easy and much better for maintenance purposes.
>
> --
> Regards,
>
> Michael Cole
> Database first - MS Access. As they are stand alone, SQL Server or
others
> like that (Sybase, Oracle) are overkill. The other options include
stuff
> like dBase, but Access is reasonably common and easy to use, which will
make
> it easier for administration - you should be able to get some people at
> remote sites who can use it if needed.
I might be tempted to use Sql Server 2005 Express if the user's don't
already have Access to save them on costs (20-30 computes times $300
for a license of Office - ouch!). I believe you could use the free
Express edition in that environment, but you should definitely check
it out first.
> Front end - VB6 with DAO access. Again - for ease of use and upgrading
of
> existing code
Again I agree - VB6 would leverage your current skills much better
than VB.Net (no I'm not trying to start a cross-language fight here).
However if you go the Sql Server route you would need to use OLEDB or
OBDC for connecting to Sql Server. Though if you don't have VB6 you
could upgrade to .Net and take advantage of the one of the free ide's
(VB Express, SharpDevolope, etc) and save yourself some cash.
Thanks,
Seth Rowe
|
