Results 1 to 20 of 35

Thread: Replace table with Userform

Hybrid View

Previous Post Previous Post   Next Post Next Post
  1. #1
    Yes I was trying to call the Unprotect and then call the Protect codes in your codes but wasn't successful.

  2. #2
    Site Admin
    Urban Myth
    VBAX Guru
    Joined
    May 2004
    Location
    Oregon, United States
    Posts
    4,940
    Location
    @paulked: It's a good idea to compartmentalize your code, such as separate routines for protecting and unprotecting, as it keeps your code modular, reusable, and easier to maintain and debug. If this were the only code ever written, then sure, just call it in the routine.

  3. #3
    Perhaps my requests have made this a nightmare of a workbook. I apologize for not making it a logical format. I think the main issue is have indirect ways of showing the data.

    Instead of one input table that the calendar fills from I opted to make the formulas pull from the other table.

    Is this the case of going back to the drawing board?

  4. #4
    I have this version which the formulas pull from the tables directly in columns U to X.

    The only issue I forsee with this will be when I have to scroll down to appointments and lose the calendar view.

  5. #5
    VBAX Master paulked's Avatar
    Joined
    Apr 2006
    Posts
    1,007
    Location
    Quote Originally Posted by Zack Barresse View Post
    @paulked: It's a good idea to compartmentalize your code, such as separate routines for protecting and unprotecting, as it keeps your code modular, reusable, and easier to maintain and debug. If this were the only code ever written, then sure, just call it in the routine.
    Semper in excretia sumus; solum profundum variat.

  6. #6
    VBAX Master paulked's Avatar
    Joined
    Apr 2006
    Posts
    1,007
    Location
    Quote Originally Posted by Zack Barresse View Post
    @paulked: It's a good idea to compartmentalize your code, such as separate routines for protecting and unprotecting, as it keeps your code modular, reusable, and easier to maintain and debug. If this were the only code ever written, then sure, just call it in the routine.
    Semper in excretia sumus; solum profundum variat.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •