Want to protect your cyber security and still get fast solutions? Ask a secure question today.Go Premium

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 447
  • Last Modified:

comparing two tables based on two identical fields

Tables:  Details, Index
Fields:  FileName, FileDate

What I would like to do is step through each record in Details, when the FileName data is identical between the two tables, the word "Present" is stored in Index.FileStatus and moves onto the next record to check.  When Details has a FileName that doesn't compare to Index, the word "Missing" is stored in Index.FileStatus and moves onto the next record to check.  When Index has a FileName that doesn't compare to Details, then that FileName, FileDate, and AppDetails (query) is run and moves onto the next record to check.  

I hope this is enough information. I appreciate any help you can provide.  I have a deadline tomorrow and this is the last piece to implement into the rest of my code and test.  Thank you.
0
mastro78
Asked:
mastro78
  • 6
  • 4
1 Solution
 
peter57rCommented:
Using a query is the simplest approach to the first part of this.
I don't understand the third bit and the second bit doesn't make sense.

QrySetPresent:

Update [Index] inner join [Details]
on Index.filename = Details.Filename
Set Index.Filestatus = "Present"

You then say 'When Details has a FileName that doesn't compare to Index, the word "Missing" is stored in Index.FileStatus'
So you want to set Index.FileStatus to 'Missing' if the record is not present in Index.  So which record in Index would you be setting to this value?

As I said I don't understand what you want to do in the third step.
0
 
mastro78Author Commented:
Actually I mistyped, there will be no need for that piece.
0
 
mastro78Author Commented:
I do have another question off topic, what is the best way to store data using a function?  I currently have a function where I'm calculating and then calling it using a text box source (ie =GetCalc).  What would be a better way of doing that so that when I open up my form, the calculation is already in place in the field.  Just a general answer will do...or if you need my code I can provide that as well.
0
NEW Veeam Backup for Microsoft Office 365 1.5

With Office 365, it’s your data and your responsibility to protect it. NEW Veeam Backup for Microsoft Office 365 eliminates the risk of losing access to your Office 365 data.

 
peter57rCommented:
If you have a calculated control it should produce the answer as soon as you open the form.
It should recalculate as you navigate from record to record or if you change any value in the record used by the calculation.  Is that not happening for your control?



0
 
mastro78Author Commented:
The calculation works, but I want to store it each time since the factors that effect that control don't change too often so I'm running unnecessary calculations.
0
 
peter57rCommented:
If the calculation is correct at all times then you should probably leave it as a calculated value.
One possible reason for storing the value would be the need to know what the value was when it was previously calculated, because the value might be calculated differently now. Another might be that the calculation involves processing 10's of thousands of records.
Otherwise don't store it.  If you do,  you can have my personal guarantee that one day the saved answer will be wrong because one of the values used in the calculation has changed but the stored answer hasn't(:-)



0
 
mastro78Author Commented:
True.  I was debating on whether or not to.
0
 
mastro78Author Commented:
I've been messing with my application to call items in different places and have basically screwed it up.  Would you mind taking a look at my code for me?  Or should i open up another question?
0
 
peter57rCommented:
I think you start another Q.  Then you will get more people looking at it.
0
 
mastro78Author Commented:
Always very helpful
0

Featured Post

What does it mean to be "Always On"?

Is your cloud always on? With an Always On cloud you won't have to worry about downtime for maintenance or software application code updates, ensuring that your bottom line isn't affected.

  • 6
  • 4
Tackle projects and never again get stuck behind a technical roadblock.
Join Now