OK Jeremy, I'll take up the challenge.
I have an app that I wrote a couple of years ago
using D3 Pro based on Paradox tables.
There are now 18 sites around the country mostly
single user but 7 have up to 5 users.
Database sizes range up to around 10
Mbytes.
Reading between the lines, on this user group, it
sounds as if Paradox's days may be numbered - not in the near future - but maybe
in 5 years or so.
The future direction of my market suggests that I
will come under increasing pressure to provide remote access to central
databases - but for low numbers of transactions.
Also the need for my clients to be able to send
each other datasets filtered from their databases is on the
increase.
Given that I am (and will always be) a newbie programmer, should I be
looking at moving this app to
Interbase
or ADO
or something else
or leaving it in Paradox for now?
What are the Pro's and Con's of each
alternative?
Over to you!
Mark
|
- Re: [DUG]: Passing the Time Mark Howard
- Re: [DUG]: Passing the Time Bevan Edwards
- Re: [DUG]: Passing the Time Neven MacEwan
- Re: [DUG]: Passing the Time Nic Wise
- Re: [DUG]: Passing the Time Neven MacEwan
- Re: [DUG]: Passing the Time Nic Wise
- RE: [DUG]: Passing the Time Colin Fraser
- Re: [DUG]: Passing the Time Nic Wise
- RE: [DUG]: Passing the Time - OLA... Colin Fraser
- Re: [DUG]: Passing the Time -... Nic Wise
- Re: [DUG]: Passing the Time Nic Wise