Would it be better having one table with all machines in a field?
yes, actually two tables - something like
tblMachines
MachinePK autonumber
MachineName text
...
...
tblIssues
IssuePK autonumber
MachineFK link to tblmachines
IssueDate date
IssueOnShift text
...
then your query would simply be
Code:
SELECT MachineName, Last(IssueDate) as LastIssueDate, Last(IssueOnShift) as LastIssueOnShift
FROM tblMachines INNER JOIN tblIssues ON tblMachines.MachinePK=tblIssues.MachineFK
GROUP BY MachinePK
The way you have it you have built data into the structure of the db. If you add another machine, you need to add another table and them modify all your queries, forms and reports. The 'correct' way means you don't need to make any changes to the structure at all, just add another record to tblMachines.
Recommend you google 'normalisation' to understand how databases should be structured