[AccessD] Future of Access?

Thanks for the input Gustav!

I'd forgotten about Oracle! I'll add that to the list of possibilities.

The requirements are (at this stage) pretty vague, but is likely to involve
up to ten concurrent users on geographically remote sites. I'm guessing on
half a million records split between five/six main tables. My current A97 db
with 16k records weighs in at (FE + BE) 15MB. My proposed db is not much
more complicated than this.

Thirty years ago my programming was done on a Ferranti Pegasus mainframe. I
had to write the programme one paper with a pencil, convert it to hole on
punched cards, wait for the technician to run the programme and give me the
paper read-out. The Pegasus (IIRC) used 60 thousand ECC83 valves (tubes) and
had a whole building to itself. Thirty years on, I've got more processing
power in my cell phone!

But my company /still/ wants me to design a database to be used for the
/next/ thirty years!

Best Regards!
Chris Foote (UK)


> -----Original Message-----
> From: Gustav Brock [mailto:gustav at cactus.dk]
> Sent: Wednesday, July 16, 2003 10:30 AM
> To: Access Developers discussion and problem solving
> Subject: Re: [AccessD] Future of Access?
> 
> 
> Hi Chris
> 
> If you are thinking of keeping the same app and database engine alive
> for 30 years I would go for Java and Oracle or DB2. Microsoft 
> is indeed
> unpredictable for a time span of this size.
> 
> However, you don't tell anything about the requirements, the amount of
> data, number of users or the complexity of the app. Nothing widely
> used - be it a programming language or a database format - disappears
> in a year; a dBase III or Paradox I application will run today which
> will have left you with at least five years considering how to port
> such an app to a present system.
> 
> /gustav