Page 2 of 2 FirstFirst 12
Results 16 to 19 of 19
  1. #16
    voodoo_ca is offline Advanced Beginner
    Windows 7 64bit Access 2010 64bit
    Join Date
    Oct 2012
    Posts
    30
    I see what you mean.

    Why would you have an additional step by adding the "phase" component?
    Im sure theres a good technical reason.

    I have people changing items in the database like when windows are complete - by entering a date for when they were done.
    If I set something to change colour when a date is added, then I dont have to get someone to also change the phase of that particular order.

    Am I not thinking the right way on something like that?

    Thanks agian for all your ideas and help.



    Chad

  2. #17
    rpeare is offline VIP
    Windows XP Access 2003
    Join Date
    Jul 2011
    Posts
    5,442
    Exactly right, if you can infer a phase from the data you're collecting, do that, if you can't infer the phase you have to add a data element that will allow you to. Just keep in mind the order in which you enter your conditional formatting rules. If you are doing conditional formatting on two unrelated fields, for instance if you want to implement a phase field but also assume that if a date appears in a certain column a certain phase condition has been met, I *think* (I've never tested) the first conditional formatting item you test for is the first that will be checked, sort of like an if, elseif, then decision tree so be aware of the ORDER in which you do your conditional formatting rules may affect your rend results.

  3. #18
    voodoo_ca is offline Advanced Beginner
    Windows 7 64bit Access 2010 64bit
    Join Date
    Oct 2012
    Posts
    30
    Ok, I understand.
    I wouldnt bother adding a "phase" field - I have enough data being entered that I can use to change the conditional formatting on things (I think).

    I have another question about the example you made.
    If I have data that I want to use as conditional formatting - lets say some windows are built on a certain date, once that field has a date, I can change the colour of the field at the beginning of the table - Do I need to show that date field in my form?
    The reason I ask is because I dont want to clutter the form with an overload of information - I only want the stuff the guy needs to make the bookings happen.

    Thanks
    Chad

  4. #19
    rpeare is offline VIP
    Windows XP Access 2003
    Join Date
    Jul 2011
    Posts
    5,442
    No, it doesn't have to be part of your form or displayed. However it MUST be part of the dataset that is running your form. So if you are running this form based on a query, the query or SQL statement must contain the element you're testing your conditional formatting against. If you're basing it directly on a table then the table should already have the element you want to test against so you should be fine.

Page 2 of 2 FirstFirst 12
Please reply to this thread with any new information or opinions.

Similar Threads

  1. Replies: 2
    Last Post: 08-21-2012, 02:38 PM
  2. Replies: 7
    Last Post: 08-03-2012, 12:08 PM
  3. Replies: 2
    Last Post: 07-25-2012, 01:01 PM
  4. Keeping Column Captions when exporting expoting pivot table
    By UofAHogs in forum Import/Export Data
    Replies: 1
    Last Post: 06-04-2012, 12:46 AM
  5. Design table - keeping worker status
    By snoopy2003 in forum Database Design
    Replies: 8
    Last Post: 02-23-2011, 12:48 PM

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  
Other Forums: Microsoft Office Forums