>Maybe relying on SQL is hurting me and I don't understand why. Can you explain what I'm missing?

No one, Ed included, is going to argue against your use of SQL. For myself I'm definitely using more and more SQL-based code.

When it comes to where to store the data it seems to be more reliably stored in one of the well-respected SQL databases. I see no reason why this should be true but it has been true of every version of dBase and FoxPro that I have ever used.

The only disadvantage that I can see to using SQL-server, Oracle, DB2, etc. is the cost. Suppose I try to market the reservation app that I have written. Most resorts that would use it would have between 10 to 30 workstations. Say I sell the app for $1000 per workstation most of which is profit. (Not necessarily the way I would market it but close enough for discussion.) If I put the data in a SQL DB my cost goes up by about $250 per workstation, significantly reducing the profit.

How have you dealt with this?

Peter Robinson