Search results

I haven't made tests - not all things are ready yet (no queries, no forms). At this stage I wanted get an advice if I am going in right direction and If don't make basic mistakes in design. I understand your post as "if it will work according to your expactations, then it is fine":) .

I made some changes in database design. I want to discuss it with you because I still missing the idea how to solve my problem. Please fallow a steps of possible scenario of user: 1. Create a statement which always at the beginning is Offer (StatementType). 2. Input Groups, then input Items and...

Ok, I took me some time for answer but I had technical problem with publushing a post with links to websites. It seems that my status doesn't allow me to do this. Nevetheless, I will try to to continue discussion. Ad. 1. Before I Start to do anything I just would like to clarify the rule that a...

- would it be correct to store these information in tblStatement or should i create separate table tblOffersOrders? Another thing: - 1 Offer can have many customers, and 1 Order can have 1 Customer. For table tblOffersOrders the relation for tblCustomer will be always 1 to many. Should I still...

Taking into consideration my above description I created db structure. Can you please advise if it make sense?

No problem. With patience I am ready for every level of details. It takes me some time to describe this model as clear as possible: Offer (or Quote or Quotation) is supplied in reply to an inquiry. It has form of letter (in my company it is simply signed PDF ), which can be addressed for many...

Offer/Order -> It means that aspect which I am describing is referring to both instances: Offer and Order. Moreover, I came to conclusion that it will be better for db to create tblStatements and for every entity I will provide StatementType (Offer or Order). It will simplify the structure...

OK Uncle Gizmo - thank you for your helpy hand, I will try to describe everything step by step. - Offer/Order consists of Group - Groups consist of Items; - Offer and Order can have versions from 0 to many (new version is created when there is a major change in the scope of the Offer or...

- Regarding design: I don't want situation that when I change something in my Order (or OrderGroup, or OrderItem), then change will be also applied to Offer (or OfferGroup, or OfferItem). I want to keep data in Offer unchanched. I need funcionality to modify Order details independently to Offer...

Thanks for all suggestion. Please find below my further explanations: Basic assumptions are: - the DB will be successor of old database for which source code and structure is unknown and cannot be recreated; - the DB must respond to the real needs and habits of users and also specific profile...

Dear all, I am developing access database to manage Offers and Orders in my company (add items, calcutate prices and to automate process of generation reports, purchase orders and other documents). I have already create a part dedicated only for Offers part. The simplify structure of already...