Search results

Welcome from an occasional visitor to VA. :p

For clarity as it seems confusing and you use the term "frequency", are services repeated? In other words, if a machine requires the 100 hour service, is it done again at 200, 300, etc hours? Or just once at 100 hours and never done again?

Like I said, mine was a brute force attack. I suspect it could be done much easier with a Gantt chart, but I have no experience with them. Search on that and see what you find.

That doesn't seem at all like the original request. I did something along these lines a long time ago to display limousine reservations on a given day. If memory serves I used a brute force method of populating a temp table with reservations within a loop. I'm sure there's a better way, I did...

I had a discussion/debate with a son-in-law about this very topic a while back. His position was that with all the automation by Amazon and other big companies there wouldn't be enough jobs and we needed a UBI. His suggestion was $1,000/month for every man/woman/child in the country. I did...

What is your code now? Do you get an error, or the results aren't as desired? If the second, what are you expecting to happen vs what does happen?

Did you try the code from the link in post 2?

How about: https://stackoverflow.com/questions/39497486/is-correct-the-code-for-bring-to-front-or-send-to-back

Note this was posted in the SQL Server forum.

Welcome back aboard!

Did you try the method from the link? Given your example above: SELECT Invoice, Sum(Total) As SumTotal FROM DetailsTable GROUP BY Invoice That's just the basics, you can add the other table and fields as desired. The key is to group by the fields you want to be unique and sum the others.

I think you want what's known in Access as a totals query. Here's a start for SQL Server: https://learn.microsoft.com/en-us/sql/t-sql/functions/sum-transact-sql?view=sql-server-ver16

Happy to help!

Welcome aboard!

I can't even bring myself to click on the link. :cry:

I use: lngLastRow = xl.Cells.SpecialCells(11).Row

You can change an option but that only fixes it on your computer. https://www.baldyweb.com/SQLWarnings.htm

I'd use this which would be more flexible (any number of inputs): http://allenbrowne.com/func-09.html

Sorry, I missed the big picture.

How about .Fields("ReleaseSingleEntry") = Me.chkReleaseALL