Search results

First and foremost review this: https://support.microsoft.com/en-us/windows/use-snipping-tool-to-capture-screenshots-00246869-1843-655f-f220-97299b865f6b Second, why do you have 2 tables with the exact same structure? That's a big error. Instead, all that data just needs to go into one...

Your table structure is incorrect. 1. Tables with the same structure. You're two tables are virtually identical. Why is that? Why can't you just use one table for this data? 2. Credits and debits in separate fields. If you want to aggregate the data (e.g. add it up). You don't store...

That's a lot of fields for a table that is properly set up. Also, "replicating data" is another sign of things not set up properly. If you have a bunch of data that is common and related, then perhaps you need another table just for that data with another table for the data that is different...

Can you expand the tables so we can see all the fields in the tables please

By focusing on forms you are attacking this the wrong way mentally. Put forms aside and focus on your tables/fields. Forms are the last element to work on in an Access database. I don't know what the right way is, but I know that is wrong. If tblStops has LoadID in it and tblStopFeeDetails...

NextCount = CurrentCount + (((CountOfRows - (CurrentCount MOD CountOfRows)) MOD CountOfRows) edit--the above finds the number greater than or equal to CurrentCount that is divisible by CountOfRows below will find number greater than CurrentCount divisible by CountofRows NextCount =...

It's a pretty simple aggregate query: https://support.microsoft.com/en-us/office/sum-data-by-using-a-query-430a669b-e7fd-4c4b-b154-8c8dbbe41c8a Instead of Summing, you get the MAX: SELECT Player, MAX(Points) AS HighestScore FROM YourTableNameHere GROUP BY Player ORDER BY MAX(Points)

So...don't update them? I still don't understand why they are unbound. Even if not unbound and you don't trust yourself to not update them you could lock/disable them on the form so they can't be updated.

Why do you have unbound fields? Shouldn't all that data be saved to a table?

My guess is 'none of the above'. Even your low estimate of 4 tables with 36 fields each is way too many fields. I suggest you post what you think one of those tables would look like. Give us those 36 fields along with some sample data and we can suggest a proper structure

Define 'work'. Not only do I not know what you have tried, I'm not really certain what you hope to achieve. "Grouping" implies a totals query. What exactly are you trying to total? How is it not working with the "Watch" group?

Again, a table has no order. You cannot rely on the way you insert data to remain that way in a table. This is not Excel. Access is a database and it operates very logically along a very logical set of rules. If you need to sort your data in a way that you can not logically do so currently...

Let's say you have this data: ID, FName, LName, DOB 1, John, Smith, 1/1/1990 2, Sally, Jones, 2/2/1981 3, Pete, Davis, 3/3/1992 4, Ron, Bush, 4/4/1983 As typed it the "middle" is between ID 2 & 3. But if you open it and its sorted by: FName, the "middle" is between John (ID=1) & Pete (ID=3)...

Huh? Count is a total. Sum is a total as well. I think the best way to communicate data issues is with sample data. So please provide 2 sets of data to demonstrate your issue: A. Starting data from TicketT. Include field names and enough sample data to cover all cases. B. Expected...

This is going to take a subquery to determine if there are any nulls: SELECT Min(IsNull([MyColumn])) AS HasNulls, Sum(MyColumn) AS ColumnSum FROM YourTable; Then make a query on that and use HasNulls to determine what to return: SELECT IIF(HasNulls=False, ColumnSum) AS YourSum FROM ThatQuery

No need to remove anything. You should pastetheDBguys code. The difference is more than just one quote mark between yours and his.

.csv - Less opportunity for crap. Weird headers, merged cells, data on multiple tabs, formulas. Ideally they'd send you a test file, you'd review and approve it and then they send you the same format thereafter. I'd do the comparison in whatever software you are more comfortable. You're on...

You're table and fields are not set up properly. The method for doing that is called normalization: https://en.wikipedia.org/wiki/Database_normalization#:~:text=March%202018),part%20of%20his%20relational%20model. Give that link a read, google a few tutorials, apply what you learn to your data...

Why are you doing this? What are you hoping to accomplish? How are duplicates getting in? The whole premise is very suspect, this isn't normally how databases are to work. Perhaps you can give us a big picture of what this database is for and what you are ultimately trying to accomplish...

Ok, second guess--Timestamp is a reserved word. Using it as a name requires you escape it in code via brackets: [Timestamp] https://support.microsoft.com/en-us/office/learn-about-access-reserved-words-and-symbols-ae9d9ada-3255-4b12-91a9-f855bdd9c5a2