Simple two table join select query but..

optionone

Registered User.
Local time
Today, 21:18
Joined
Feb 11, 2010
Messages
56
.. I need to restrict 'usage' of the second table so that when a match is found the particular line in the second table doesnt get used again

(as you can tell i am still rather new to access)

Is there some easy way to do this? Or am i going about this the wrong way with a join?

Thanks :D
 
Not sure what you mean. If you could provide the scenario, a set-up example and the objective it might be helpful for a good response.

-dK
 
Hi - sorry you are right - shall try to explain better..

The database processes product spend and credits - source data is provided to me and unfortunately can not be altered - this source data is unfortunately not all that accurate as it is just a dump of 'what has happened' so includes wrong issues etc. What I am trying to do is eliminate these wrong issues by either removing the issue and corresponding credit line or by zeroing the value for both these lines so they dont get charged out and then credited back

Data fields look like this:

Code:
[FONT=Arial][SIZE=2]issuedate[/SIZE][/FONT]
[FONT=Arial][SIZE=2]clientname[/SIZE][/FONT]
[FONT=Arial][SIZE=2]clientnumber[/SIZE][/FONT]
[FONT=Arial][SIZE=2]costcentre[/SIZE][/FONT]
[FONT=Arial][SIZE=2]product[/SIZE][/FONT]
[FONT=Arial][SIZE=2]quantity[/SIZE][/FONT]
[FONT=Arial][SIZE=2]return[/SIZE][/FONT]
[FONT=Arial][SIZE=2]issuetype[/SIZE][/FONT]
[FONT=Arial][SIZE=2]location[/SIZE][/FONT]
[FONT=Arial][SIZE=2]value[/SIZE][/FONT]
[FONT=Arial][SIZE=2]comment[/SIZE][/FONT]

Trouble is although an issue line would have all those fields complete - the credit lines (if the issue is returned and has a return field filled in) only has a few fields - issuedate, product, quantity, (negative) value and comment. Some credits take their time to be processed and as this data is provided to me monthly the credits can sometimes slip to the next month or later months if not noticed

As such even on linking credits to wrong issue on all fields avaialble there might be a disproportionate amount to - eg. there might be 2 wrong issues but only 1 credit - but the credit will link to both wrong issues

Hope I havent made this too difficult to understand - essentially i am trying to match and 'cross-off' one credit per 'wrong' issue and not have multiple matches

Thanks
 

Users who are viewing this thread

Back
Top Bottom