Query Criteria for a report

[sjs94704]

I have a client that I made a database for with Purchase Orders. He wants to call them purchase Orders instead of Invoices (whatever).



I have two reports created, Sales by Customer and Sales by Account Manager. I have two fields on the reports menu for Start Date and End Date.

The queries for each of these reports looks at the Start Date and End Date just fine.

Now, the client wants optional criteria of selecting all customers or a specific customer, or all Account Managers or a specific Account Manager.

the fields are CustomerID and AccountManagerID.

What would the criteria code look like for each to give the user a choice as specified above?

[alansidman]

does this video help you?

alan

http://www.datapigtechnologies.com/f...mtoreport.html

[orange]

sjs94704,

Alan has given you a good video tutorial that should help with an approach.
I'm sensing a little a little hesitation or reluctance on your part to alter your current project.
I may be reading more into your post than was intended, but this sort of thing

He wants to call them purchase Orders instead of Invoices (whatever).

and

Now, the client wants optional criteria of selecting all customers or a specific customer, or all Account Managers or a specific Account Manager.

reminds me of an old British saying about their railroads --" The trains would all be on schedule if it wasn't for all the damn passengers".

Clients often want more, and more often than not they really aren't sure of exactly what that is. You have to adapt, and clarify vague requirements. Communication and feedback are necessary because - if you and/or the client can't describe it, you nor anyone else can build it.

You are dealing with the edge (perhaps early stages) of somewhat poorly defined process.

Here's a quote (from wikipedia) and a link :

In many business models a contractual relationship is established first via a Contract or Subscription. Orders are then received via different sales channels, such as phone, fax, email, internet or sales person. The contractual relationship is confirmed and the Orders are fulfilled through shipping and logistics. On completion of key events an invoice is generated and booked as Sales (subject to "Revenue Recognition" requirements). If payment has not already been received, the debt is recorded and pursued through dunning cycles until the funds are received. Order to Cash is completed by the Customer Care process (enquiries, requests and complaints).
If we consider the ERP system flow, this is typically categorized into the following seven sub-processes:

• Customer presence
• Order entry (creation of order / booking of order)
• Order fulfillment (physical & digital fulfillment)
• Distribution
• Invoicing
• Customer payments / collection
• Cash Application
• Deductions (If invoice Short Paid by Customer)

Here's the link to the article so you can activate the embedded links -
http://en.wikipedia.org/wiki/Order_to_cash

Here's an existing data model that shows many of the "entities" involved.
http://www.databaseanswers.org/data_...ders/index.htm

and another
http://www.databaseanswers.org/data_...ices/index.htm

Good luck with your project.