RE: Stear me in the right database direction

new topic     » topic index » view thread      » older message » newer message

1. What is your intended application: web, desktop, single-user, 
multi-user?
Desktop is what I have always done although Web would be interesting.

2. How many transactions per day do you expect?
After the intial data input maybe 100 lookups per day. Data would be 
maybe one entry per week. The database would grow slowly after the 
initial setup.


3. How many GB of data do you expect to add to the database in a year?
Initial database size about 50mb since I would probably store the jpg 
files seperatly. Doubt the DB would ever exceed 500mb

4. What platform will you be running the database on?
If desktop then win xp

5. What platform will you be running the application on (depending on 
the size,
this may or may not be the same as the database)?

I guess I would like to use Euphoria because I am familiar with it & 
using sequences suits me.
A>Can I use EU to power a web based DB program. 

B>Can I still use EU's DB format as again I am familiar with it.

C>If so I don't know how to do this, I have seen some stuff on using EU 
as a CGI type script but dont have a clue how to go about setting this 
up.


Thanks

Tony


Michael J. Sabal wrote:
> 
> 
> posted by: Michael J. Sabal <m_sabal at yahoo.com>
> 
> Tony Steward wrote:
> > 
> > Hi all,
> > I want to create a data base which has a handfull of tables. The main 
> > table will have one to many links to most of the other tables but ine 
> > link will be a many to many relationship. This database would hold text 
> > and pictures. Preferably JPG.
> > 
> > What direction / system would you use. I have considered MS Access but 
> > would like to write my own.
> > 
> > Any comments please
> > 
> > Thankyou 
> > 
> > Tony
> > 
> > 
> Virtually any database system out there would handle this in one way or
> another, including Euphoria's database system.  The key questions are
> 1. What is your intended application: web, desktop, single-user, 
> multi-user?
> 2. How many transactions per day do you expect?
> 3. How many GB of data do you expect to add to the database in a year?
> 4. What platform will you be running the database on?
> 5. What platform will you be running the application on (depending on 
> the size,
> this may or may not be the same as the database)?
> 
> If you're interested in the learning experience, feel free to roll your 
> own.
> Database.e, included with Euphoria, is a great place to start.  If 
> you're
> really only interested in the end result, use an existing package and
> odbc or api wrappers.
> 
> HTH,
> Michael Sabal



Give your hardest tasks to your lasiest workers. 
They will always find the easiest way to complete it.

new topic     » topic index » view thread      » older message » newer message

Search



Quick Links

User menu

Not signed in.

Misc Menu