Editing Data within a Query

AC5FF

Registered User.
Local time
Today, 06:35
Joined
Apr 6, 2004
Messages
552
I know that it is possible to edit data when a query is run; I have several queries that work just fine and they allow me to edit the data right there within the query. These were created long ago.

However, I have written a new query but I cannot edit the data - and i need to be able to with this particular one.

I've looked at properties, type, etc etc and I cannot seem to find a difference. They are all select queries... Just not editable..

Any ideas?
 
Thx Spikepl...
I'll have to go look at the other queries I know I can edit; but that website shows me why I can't edit the current one.. :) I've got a union in this query..

Maybe you (or others) may know how then I can pull out the data from one table that does not match data from a second table. I'm using this query to verify accuracy of data entered into a table. If my account number entered is not within the accounts table I need to correct that entry.
Right now my query pulls all the data entered, and I just sort the data where the account information is not correct to the top. Right now that's 36 records out of 1476.

Here's the SQL of the query as it sits now...

Code:
SELECT [TIME SHEET HOURS].DATE, [TIME SHEET HOURS].[EMPLOYEE ID], [TIME SHEET HOURS].[ACOUNT NUMBER], Accounts.[Acct Number], Accounts.[Account Name]
FROM [TIME SHEET HOURS] LEFT JOIN Accounts ON [TIME SHEET HOURS].[ACOUNT NUMBER] = Accounts.[Acct Number]
WHERE ((([TIME SHEET HOURS].DATE)>#1/1/2011#))
GROUP BY [TIME SHEET HOURS].DATE, [TIME SHEET HOURS].[EMPLOYEE ID], [TIME SHEET HOURS].[ACOUNT NUMBER], Accounts.[Acct Number], Accounts.[Account Name]
ORDER BY Accounts.[Acct Number];
 
Last edited:
I'm using this query to verify accuracy of data entered into a table. If my account number entered is not within the accounts table I need to correct that entry.

Is there a reason why you don't verify this at the point of data entry and prevent the invalid data from getting into the table in the first place?
 
Beetle;
I agree with spike - this should be verified at entry.
The DB was set up before I took over the position and updates like this was set up to be entered directly into a table without any links/verification. Had I designed it, I would have put the links in so that the data was verified as it was entered. I hadn't gotten to the point of editing things that far yet.. May have to though - as that would save me time in the future.
 

Users who are viewing this thread

Back
Top Bottom