Search results

Your database seems simple enough, but there's a few things I don't understand. 1. Only one item goes to an invoice? That seems different from every other invoicing system in the world. Usually a system like this has 4 tables--Clients, Items, Invoices and InvoiceItems. That way an invoice...

Doc doesn't want to belabor the issue, but after your two recent posts it seems someone has to: 1. Type is a poor name for a field. It is a reserved word which will make coding and querying more difficult later on. You should prefix with a word that the type represents (e.g. SalesType...

I only use unbound forms for menus. If I want the user to act on the data (create, update, delete) I use bound forms. Even if I want the form to be read only but I wanted to display a lot fields from a datasource I would still use a bound form, but just disable everything. Bound forms are easier.

When you have ties there's no predicting how its going to sort. If you want to ensure the same sorting you should add a unique field in addition to the date one.

Also, who cares? Why must your numbers start with a particular value? Autonumbers should only be unique. If you have that they will serve their purpose. If you are using them for another purpose other than uniqueness, you shouldn't. So, what exactly is the issue if they don't start with a...

Disregarding the issues pointed out before, here's all the issues I see with your date logic: Case 48 'All Dates [CkDate] The above will actually work but not for the reasons you think. It's going to resolve to "...WHERE 5/27/2025..." and whenever you don't have an actual comparsion...

Totally agree with jdraw. Here's the 2 codes that set those 2 boxes on your form: ... txtSI_FIFO = Nz(DLookup("[SoldQty]", "[TblFifoSummary]", " [ItemCode] =" & [Forms]![Form1]![Combo1] & " "), 0) ... txtSI_Qry = Nz(DLookup("[SumOfxQty]", "[Query2]", " [InvType] =2 "), 0) ... They are...

Agree with jdraw and also recommend working on populating your tblPropertyTypeAttributes table so we can see your attributes. Some attributes may not need to go into there if they are attributes that all Properties have. For example if you wanted to know the number of bedrooms you wouldn't...

Quit throwing files at us we just want you to explain your data. Here's the last of the help I am giving: What you want for Number Of Repetitions is called a "Running Count" search this for that term and you will find the method to achieve that. What you want for Sum Of Count, is just...

1. AA03 was not the selected partnum I wanted to examine, AA02 was. We are paying attention to you and your issue, please pay attention to our posts. 2. Does that mean you posted incorrect data initially? Row=4, PartNum=AA01, Number of Repetitions =1, Sum of Count=1. Shouldn't they both be...

Boy that was not helpful. You simply removed selected data from your initial screenshot which I have access to. You need to hold my hand verbally and explicitly describe how each value is arrived at. Revisit my question and explain in detail how each value for the specific record I selected...

Walk me through one specific calculation: For Row=5, PartNum=AA02, NOTE=Ready; explain why number of repetitions=2 and Sum of Count=3.

My guess is you put every field in the GROUP BY. You only need to put things in the GROUP BY that you want to....group by: SELECT IDTicket, COUNT(IDTicket) AS Total FROM YourTableNameHere WHERE Status=1 GROUP BY IDTicket If neither June nor I are correct, you need to post what data you...

No, not if you are using a MAKE TABLE query to create a temporary table and just passing a field named 'ID' through to it.

Why is this an aggregate query without any aggregate functions? GROUP BY is most often used for totals (SUM, COUNT, MAX, etc.) but you use none of those functions in the SELECT. The other reason is to use GROUP BY is to eliminate duplicates. Are there duplicates when you don't GROUP BY? If...

Yes very pedantic. I was talking about the extraneous '0' in your post. It doesn't detract from your post or point (in fact, I bet very few even conciously saw it until this sentence explicitly pointed it out), but on this site people can't stop themselves from pointing it out to no real...

The worst, especially on technical sites like this, is when someone feels the pedantic need to point out inconsequential errors that neither correct nor clarify anything and add nothing to the conversation other than showing that the poster geniusly spotted something out of place.

Just initialize FilterSTR to an always true comparison and then whenever you want to add a criterion to it always start it with " AND" FilterSTR = "(1=1)" iif (Isnull(Something)=False) then FilterSTR = FilterSTR & " AND ([Something]='" & Something & "')" iif (Isnull(SomethingElse)=False)...

I suggest you go to Pat Hartman's original numerated response (Post #2) and address what she brought up number by number. Either tell her that you agree with each and every point, or explain why you disagree. Go point by point to each of her numbers in that post. Then we can move on to forms...

That explains the datatype but not what the data represents. What does that date/time represent in the context of each table that field appears in?Why is it necessary? Lasty, and most importantly, you're just throwing things at us. Posted a schema, thoughtful notes were giving, you briefly...