When I think back to the dozens of Access applications I've created, and the
single ASP application I've created that used Access, I can safely say that
I've never onec had to worry about whether a field was "Required" or not.
The reason: I never created a nullable field. And even when i was using a
database created by someone else, I did not care: I always put a default
value into all fields. Instead of wasting devlopment and processing time
with code code that tests the nullability of the fields in your table, start
with the assumption that they are all required.
Having said that, I'm wondering if you realize that an Access Text field can
be created with the Required checkbox unchecked, but the "Allow zero-length
string" checkbox unchecked, a contidtion which will not be covered in the
Attributes property since it's a Jet-specific property.
Bob Barrows
Lorenzo Bolognini wrote:
"Aaron Bertrand [MVP]" <aa***@TRASHaspfaq.com> ha scritto nel
messaggio news:uJ**************@TK2MSFTNGP09.phx.gbl... Make sure you are using OLEDB to connect to your database;
adFldIsNullable is not exposed to the standard ODBC/JET drivers. To
see an OLEDB connection string, see http://www.aspfaq.com/2126 and
make sure you have a recent installation of MDAC.
The following is my connection string and i'm using ADO 2.8 on a
Win2k with ALL the latest patches:
cnn.ConnectionString = "Provider=Microsoft.Jet.OLEDB.4.0;" & _
"Data Source=" & Server.Mappath("\xxxy\datasource\xyz.mdb") &
_ ";Persist Security Info=False"
I'm noticing that someone else has had the same problem always with
Access as you may see if you look for this MsgID:
uGwIzjTjBHA.2024@tkmsftngp04 on microsoft.public.data.ado