You can see my confusion, unless you're a programmer. JP, I've been looking through the posts and can't find basic info on the capabilities of the field choices. How long can a single text field be (how much text can we store in the file)? Also, I noted on your JP Deni home page that you're no longer doing customizations. Why? I really admire the help you've given people here. Worn out? I sense that DBman is stretched to the limit to do all the things that folks want it to do. And that you help them with. It's really quite impressive. I'm wanting to do a simple job postings page for a company to show jobs available. Know of developers that'd be interested?

------------------
--MJ

M John,

I don't think there is a field size limit. I've set one of mine to 5,000 and it works fine.

Thanks KM, boy you were up later than I was. Can you explain the "not null" option. It refers, I think, to "Can a user leave this blank? How can I frame the question I think of in my head so that I get what I want if I check Y or N?
Also, what are the reletive merits of just using an mySQL for these kinds of tasks besides response times. Does DBman really help bring a lot of development functionality to the table?

------------------
--MJ

If Not Null is set to 1, that means your customers must complete that section of the form. Im not sure about your SQL question.

One way to look at "Not Null" is to think of it as "Required." If a field is required to be filled in, set "Not Null" to 1.

The functionality of DBMan-SQL is the same as with DBMan. SQL is just faster.



------------------
JPD