*** Quoting Sean Dennis from a message to Mike Roberts ***

 SD> Are you trying to say that I'd not listen to you? :/  Eh, I'm always
 SD> willing to listen (see below)...

Why soitaney.. I'm insiniatin!

 SD> No, actually, you're right -- I had to go into BW and manually add
 SD> the correct write permissions to each and every base according to how
 SD> I have it set up in Max.  In Max, it uses the same ACS for read/write
 SD> (I believe they're both able to be set, but I can't remember right
 SD> now).  But in BW, it just reads the initial settings and doesn't
 SD> change it.

As I say, I don't know how max works, but I know You know TG and the other 
system was similar. If there is a write access like in TG and You don't want 
or need to get fancy. Lets face it there is not a million people fighting and 
clawing to get in and mess up your message areas like in days gone by. Don't 
worry about setting a write access in Max ( if it does such a thing ) set it 
to nil, unless You need to let somebody in that you do not want to post, but 
to read. I may be just blowing smoke as I don't know max. But in the 
situation I was thinking of, if You set post access to nil, then BW allows 
the post. this sounds like what You did though. set the r/w to nil in max. If 
that is not what You did, see if that works. Worst that could happen is 
somebody posts in a fido echo that should not, But that is rare these days. I 
hope it works out for You, if not, that whatever you do do, does.

Good Luck!
Mike

... You know you're dieting when postage stamps taste good.

--- Telegard v3.09.g2-sp4/mL