If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below. |
|
|
Thread Tools | Display Modes |
#8
|
|||
|
|||
a Challenge for me
i reallly appreciate your help thanks for all of you but still let make it
more clear i am not satisfied what i want ....... let make it more clear i will have two tables; one for purchases and the second for sales to give you the idea about the stock . for example [purchases table] SNO Item Serial Starts Serial Ends 1 Talk Home 87564561 87565060 so the above stock is 500 cards with me in stock lets supppose i sold the following 60 cards randomly in [sale table ] such as SNO Item Serial Starts Serial Ends 1 Talk Home 87564581 87564590 2 Talk Home 87564640 87564690 however there are two transaction now in the sale table where in the first transaction i sold 10 cards while in the second transaction i sold 50 cards so the question is that how i would know in the system that which cards serial number are in my hand when slowly i sale more cards. hopefully it is more clear now thankx in advance "Fred" wrote: Dear Naveed, I believe that I do understand what you are saying. And, if you will forgive me, that I may have thought through the possibilities within what you are saying more than you have, and so might understand what you are asking even better than you do. :-) Is this correct: You are saying that you typically start with a group opf items of the same type, but each with a different serial number, and typically a set of sequential serial numbers. And that any one of these items may get sold /removed. (e.g you can't dictate that they take the lowest or highest serial number.) And, you have given us an example, where someone has taken one out of the series and want the datebase to show you whic ones are still in stock. And since the PARTICULAR example that you have in mind (just one missing) is where the missing one is an exception, you are imaging a system which will serve for that example, I.e. to say "1 through 87" and 89 thought 100" are in stock. And so you are imaging some systems that will base it's answer based on where the (one) "gap" is. You probably haven't thought about the more complex scenerios, e.g where someone has removed the following serial numbers: 3,5,8,11, 22-29, 35, 39, 45--49. 51. 55.56. 61, 70-75, 85,86, 93, 94. And, you have probably made the common error of thinking that this can be solved without starting from the ground up by desigin a table structure that will support accomplishing what you are trying to do. I.E. making the mistake that you can skip this table structure step and go right to the finish line of what you seek via some query or form action. If all of my guesses are correct, then my previous post would give you a foundation that would be a good starting point for solving this. More work would be needed after that, but it would be a foundaiton. |
Thread Tools | |
Display Modes | |
|
|