Jump to content

beju0506

Newbies
  • Posts

    2
  • Joined

  • Last visited

beju0506's Achievements

Newbie

Newbie (1/14)

  • First Post
  • Conversation Starter
  • Week One Done
  • One Month Later
  • One Year In

Recent Badges

0

Reputation

  1. Soren, Actually, that DOES help! You just gave me an idea... I'll give it a try and let you know if it works out. Thanks! -Justin
  2. Hey everyone, I apologize if something like this has been asked before, but I haven't found anything using the search function. Here's the scenario: We import records of software installed on computers owned by our college (collected via RemoteDesktop) into a table in the database. We want to keep a reference list of some sort that labels a particular software as "important" and that it should come up in our reports/portals. Basically, the simple description is that we want reports and portals to "check" the list and see if a software is marked as important, and if so, show it in the report/portal, otherwise not. I'm posting because I'm looking for advice on how to best approach this. We do have a separate table that has unique records for each software (that holds license information, etc) and we can use that to link to mark the software as important via a checkbox. We could then use a relationship to link to the individual software records and store a Yes/No value via a calculation. This is our current best solution. However, we're a little wary about basing all of the links on calcs like that... Plus it causes issues in our website (using calcs to determine relationships). Does anyone have a better suggestion/solution? Do you have something similar in your databases? How do you do this? One major issue we're facing is that the names of the software that are imported via RD and the names of the software in the database are not exactly the same. We could create a field in our software titles table (the one that holds a unique record for each software) that could link to the software name that comes in from RD, which would be easier than doing so for each individual software record. Sorry if this seems convoluted, it's a bit difficult to explain. Any suggestions you can offer are greatly appreciated! -Justin
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.