Re: [Tutor] DB design

2005-02-18 Thread Victor
Liam Clarke wrote: Anyway, why don't you tell us more about what you are trying to do and we can give better suggestions. Kent Database organised - Client details Jobs Finances | | |

Re: [Tutor] DB design

2005-02-17 Thread Liam Clarke
Hi, > > Anyway, why don't you tell us more about what you are trying to do and we can > give better suggestions. > > Kent I told you it was vague. ; ) Ok, so if you'll tolerate some bad ASCII, I've been narrowing down what I want to do, and I think it's like this.

Re: [Tutor] DB design

2005-02-15 Thread Alan Gauld
> I'm already hitting my conceptual troubles however, as I'm visualising > each table as a 'card'. Maybe but the cards are made up of rows, each row with fields. Think like a spreadsheet. Each sheet can have references to other sheets - like Tabs in Excel > dimensional. But what I was wonderi

Re: [Tutor] DB design

2005-02-15 Thread Bill Kranec
Liam, I think what you want is called a view. A view is a memory based table defined by a query as follows: CREATE VIEW myview ( column1, column2, ... ) AS BEGIN SELECT * FROM table1 END; In this example, you can now SELECT * FROM myview, and get table1. You can put joined tables or

Re: [Tutor] DB design

2005-02-15 Thread Kent Johnson
I don't think you can do exactly that. But SQL does have powerful capabilities to do selects on multiple tables at once. It's called a 'join' and it is very common. For examples suppose you have a customer database with a Customer table: cust_id cust_name 111 Liam Clarke 222 Kent Johnson