OK. Never mind. I played with the Intellisence (if that's what CTRL+Space is called) and it all pops up.
Tail 'tween leggs, Steve
--- In ExcelVBA@yahoogroups.com, "noskosteve" <noskosteve@...> wrote:
>
>
> OOPS... Re-reading your answer, this appears obvious. I I guess a better question is: "Are there any other options to the 'protect' procedure?
> Steve
>
>
> --- In ExcelVBA@yahoogroups.com, "noskosteve" <noskosteve@> wrote:
> >
> >
> >
> > --- In ExcelVBA@yahoogroups.com, "Pascal" <pascaldaulton@> wrote:
> > >
> > > another two possibilities:
> > > 1. Have a line in the workbook open event:
> > > Worksheets("Requirements").protect userinterfaceonly:=True
> > > (I 'm not sure whether you'll have to supply the password as well.) This will allow vba to manipulate data on that protected sheet without it having to be unprotected and later re-protected.
> >
> > A bit'o clarification here please.
> > This is Very interesting. I've used the unprotect-do-work-then-re-protect, but sshould an error occur, you're left unprotected. This looks better.
> >
> > Just to make sure...
> > This is saying that only the user interface is protected, right?
> >
> > What is then unprotected, the VBA "interface", thus VBA can do things?
> > Steve
> >
>
Be sure to check out TechTrax Ezine for many, free Excel VBA articles! Go here: http://www.mousetrax.com/techtrax to enter the ezine, then search the ARCHIVES for EXCEL VBA.
----------------------------------
Visit our ExcelVBA group home page for more info and support files:
http://groups.yahoo.com/group/ExcelVBA
----------------------------------
More free tutorials and resources available at:
http://www.mousetrax.com
----------------------------------
Tidak ada komentar:
Posting Komentar