Been asked - yes, pursuaded - no
Last one a couple of years ago was for a theatre company - an employee had built it using only macros and no documentation. And data wasn’t properly normalised. It handled show bookings and some elements of production and staffing rotas. They wanted to license...
about 20 years ago I was involved in migrating an access system for calculation of sales commission for around 600 sales people. It used to take about 1 1/2 hours to create 600 reports and email them to each person with copies to managers. The new boy on the block decided that access was not a...
The problem i have with the new browser control is that when using it to display local files. updating the control source doesn’t always refresh what is displayed
can't say I agree with all those comments
Why "1" is better:
Faster - Access doesn't need to resolve field names
No field name conflicts - Won't break if you rename/delete fields
Clearer intent - You're just counting records, not referencing actual data
Performance comparison:
you don't do...
So usual reasons for moving to sql server BE, nothing new. Now if only IT could actually support the typical rapid changes required to meet strategic initiatives, particularly when only 5 or 6 users out of say 500 users require the functionality. As it is with companies that have low data...
dcount will return the number of lines in the query. If the query already has the criteria '"received" = False' then you just need
DCount("*", "TotalOpenPOQuery")
What I have done in the past when migrating data from one system to another is to create a migration document. This lists all the tables and fields in the new system together with all datatypes and constraints. Sometimes with performance criteria as well.
The old system tables and fields are...
usually means you have a spelling issue so first check names - TotalOpenPOQuery and OrderID - and is orderID on your main form?
try using Me.OrderID to verify
and try using "*" rather than "1" in the dcount function
doesn't matter - a form does not have to have a recordsource. It can have unbound controls or controls bound to a calculation/function such as dcount. And as Arnel shows, you can assign a value to a label or button by assigning the value to the caption.
The potential problem with having...
Given this has come about as a result of UK law, I was going to suggest ‘the speaker’ as in the speaker of the House of Commons- the person who slaps down inappropriate behaviour of MP’s
Perhaps you should also clarify what you mean by access procedure - a specific sub or function? Doing what? Is access split? If so where and what is the back end?
Why use a subform in the first place? Is the idea that it expands if the user clicks on it?
Why not use a label or button? - I do something similar to show certain data and use color to indicate current status. Eg red might mean invoices to be raised or paid - user clicks on the label/button to...