- Local time
- Today, 14:15
- Joined
- Feb 28, 2001
- Messages
- 27,183
sorry to be rude but i know exactly what i'm doing and my table structure are perfect
I am truly glad you figured out a way to solve your immediate problem. You do, however, have a very serious long-term problem. I mean no disrespect, but you are making a very common error and it will continue to hamper you. You see Access and think Excel. This is wrong. Let me try to illustrate by analogy.
When you think of documentation, it is perfectly true that you can turn off borders and do other sorts of "diddling" so that you could write a nice document using Excel and even make it look pretty. But you should be writing documents in Word, not Excel, because they are different programs with different viewpoints. Does that make sense?
Similarly, Access and Excel are two programs written with radically different viewpoints. The difference is based in structural relationships and uniformity of data. Technically, all Excel cells are independent of each other. You can do things to cells as a group, such as forming horizontal or vertical sums. Leaving a cell empty or blank will not screw up a formula. The functions in Excel include ways for you to aggregate bunches of cells in various ways. You can even make a cross-cell reference so that a given bunch of numbers are repeated elsewhere on the same spreadsheet.
With Access, though, the utility program that is the Access user environment (which we call the GUI) expects a more formalized structure to the data you give it. Here is a simple comparison:
In Excel, you can have a string of number-filled columns and right in the middle of that spreadsheet, toss in a blank line or two and then start a new set of data IN THE SAME COLUMNS - but use data that is all text, not numeric. The fact that rows 4-64 are numbers and rows 70-99 are text for the same columns means nothing to Excel - but that cannot EVER be done in Access.
Therefore, you are asking Access to do something it wasn't built to do. I have no doubt that your databases ARE perfect - for Excel. But as you described them, they are nowhere near perfect for Access.
I don't want to upset you or insult you, but I have to tell you that your horizon doesn't reach far enough. The Bard of Avon put it this way: "There are more things in Heaven and Earth, Horatio, than are dreamt of in your philosophy."