Jump to content

CalvinFold

Members
  • Content Count

    14
  • Joined

  • Last visited

Community Reputation

0 Neutral

About CalvinFold

  • Rank
    novice
  • Birthday 01/12/1971
  1. Actually the kind of feedback I was looking for. Knowing how my department works, anything I can do to "futureproof" or "modularize" or make more flexible, just in case, usually is worth the trouble. We tend to "shock develop" way too much (get it done *now*, messy or otherwise) and then pay for it later when modifications require re-writes of large chunks of things. When I get the rare chance to take my time, do things right, and plan ahead, I try to take advantage of it. Spent weeks on this one just getting a proper ERD together in Visio and reviewing with a good friend and databas
  2. To both [color:purple]comment and [color:purple]Genx... From a strict point of view, from that "best practices" kind of view, which is better: doing this via calculation or via a relationship? Mind you, calculation may be simpler, but that's not what I'm asking. For example, using Surrogate keys is often way more annoying than Natural keys, but in the end are generally "better" from a design standpoint, and often required in corporate environments. In my case it's "best practices" for database design for my company. (Okay maybe not the best example from a professional point of
  3. HUZZAH! That worked! The popup in my layout to create a new [color:brown]networkAccessTable record is giving the expected values. Of course this solution caused another layout to start showing the key field instead of the value, but that I should be able to suss out. Also need to really sit down are stare at what you just showed me to be sure I understand the trick, rather than just knowing it by rote. I'm still curious about [color:purple]comment's method, which is also interesting. Much, much thanks!
  4. Can you explain what's going on in yours? It seems to do what I'm after but I'm trying to figure out what [color:brown]cActiveValueID is doing exactly and how it all fits together so I can put it into my database properly. It does seem simpler, but I want to understand it in case there is a catch for my particular setup. THANKS!
  5. There must be a piece of the puzzle I'm still missing, some setting or concept my eyes and brain are skipping over. (My apologies if this is "dragging"...but this isn't covered in the five different reference books I have here at my desk. I honestly do try to beat my head against these things first before coming to forums.) Three screen shots attached. One is the Relationship dialog as I've got it set. The other two are the two different ways I've tried the Value List. One is all values, which will cause the popup to display all values, whether Valid or not. The second shot was just
  6. Define "main." Technically, both these tables are sub-tables in a much larger framework. I'm building bottom-up. In this pairing, it works left-to-right, with [color:brown]networkAccessTable is the "main" table, with [color:brown]networkPortLocationList only serving as a means to dynamically manage a popup list (i.e. it stores the values). The two tables suffixed with "_Self" are instances of the table with the similar name they are joined to and are simply for user interface purposes. [color:brown]zdev_utility is just a place to stick global utility fields, mostly for user inte
  7. I've attached a screenie of the Relationships screen. For your purposes, ignore the extra table instances with the "_Self" suffix. Those are self-joins needed for a user interface trick I'm using and don't affect anything else.
  8. Unfortunately I'm not at liberty to post the database due to company policies. If you need details, just ask, I may be able to provide screenies or descriptions. Sorry. Can you give me an example using only TWO tables so maybe I can figure out how to adapt it from that example? On a side note, I appreciate the "1" and "0" thing. But there is an off chance I may need intermediary levels besides "on" and "off" in some areas and I wanted to be consistant with terminology. I find real-English easier to use when I have long gaps between working on the project (something always seem
  9. I set-up the relationships in my database per your example (using the constant) but the relationship does not seem to affect how the popup displays values. It's still displaying values with a ValidState of "Obsolete." I noticed your example is a three-table system, whereas mine is a 2-table system: netPortLocList This table stores the possible popup list values for the other table: __kp_netPortLocID (key field) zrec_ValidState (whether a value is "Valid" or "Obsolete"...there are no value deletions for history tracking reasons) netPortLocValue (the list value) Some other
  10. Wow, is that really the only way to do it? As I understand it, in order to "filter" the relationship I will need to have a field for every "filter value" I wish to use. That sound about the gist of it? That just seems "messy" somehow, especially since I'll have to repeat this technique alot in this database. But if that's my only option... *shrug* Would there be any problem setting the field to get it's value from a custom function? My thought was to put the filter value (in my case, "Valid") in a custom function like a database-wide constant. That way, if for any reason it
  11. I can't seem to figure out how to add a calculation to a relationship. I get the dialog with the tables and their fields on the left and right, and an operator popup in the middle, but no way to enter anything else. I assume I'm missing some critical detail again. Apologies in advance for the n00bishness...first time I've ever had to do such complex relationships.
  12. Followup question: Given the above relationship and popup list... Instead of physically deleting obsolte or invalid entries in PortLoc, I have a ValidState field that says "Valid" or "Obsolete." Is there any way to build logic into the relationship so that the popup in AccessTable only shows the values that are marked as "Valid" and does not show the values that are marked "Obsolete"? Even more advanced I suspect, is that ideally any values in AccessTable whose values have been marked Obsolete in PortLoc should also be flagged somehow in AccessTable as needing attention (i.
  13. Sorry it took so long to respond, I wear alot of hats around here... Can you give me some places to look if I did the above (which is what I had also suspected I'd have to do) and it's still static and not dynamic? If I have something like... ID = 1 Value = 2nd Floor ...in the PortLocation table when I make the selection in Access Table, then change the Value in PortLoc to... ID = 1 Value = Second Floor ...the popup in Access Table still says "2nd Floor" (the originally chosen value). Is this some sort of storage issue? Or is something missing from my def
  14. I just *know* I'm missing something obvious, but I've never done this style of value list before. Apologies in advance if I don't post my file, but it has my company name splashed all over it and it's internal... I have two tables. One of them is designed to hold onto values to be used as a value list in the other table. The idea is if an edit is made to a value, that value changes everywhere it was used in the other table (i.e. the field value changes but the key value remains the same): TABLE: networkPortLocationList __kp_networkPortLocationID (primary key) netPortLocValue (li
×
×
  • Create New...

Important Information

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