Razzak: I'll tell ya why I designed a table with 747 columns -- short answer, because the client paid me to <gr>. No, actually here's why -- this client has NO programs written in RBase. None at all. They have a couple crappy forms designed in-house (converted from old DOS forms apparently), but when I asked about them, they said "oh, we don't use those forms anymore". All of what they do is straight from the data browser. They use a consultant (me) an average of 5 hours a year and are proud that they have such a "simple" system and they don't have to learn programming or hire a consultant. They use RBase as a glorified Excel spreadsheet, and that's the truth. On the other hand, they might know more about QBE and getting stuff out of a data browser screen than I do!!! I spent alot of time pushing a vertical table structure, and in the estimate I gave for creating this huge table I wrote in the estimate that I would never recommend creating such a table on my own. Money is not the issue at this company -- I would have to change the entire department's concept of working, and telling them that they would have to hire me to design forms and reports for this table wouldn't make sense to them if I am able to create a spreadsheet-like table of 747 columns like what they want, which is within the advertised limit.
Karen > On the other hand, good database design is the key. You will never see > any problem with a properly designed R:BASE database. (Why in the world > would you design a table with 748 columns?). There are more eloquent > methods to design a database and to achieve the desired results. > > Having said that, before drawing any conclusions, the user or developer > needs to
