Upsize no longer transfers "Required" fields to Not "Allow Nulls"

[Guest]

Hi everyone,

I have been working on upsizing an Access 2000 data structure to SQL Server
2000 using the Upsize Wizard in Access2k2/XP. I have been developing the
data structure (no data yet) in Access, upsizing, reviewing the results,
tweaking the structure in Access, then repeating.

So far so good then, all of a sudden, the Access fields that have "Required
= Yes" stopped showing up in SQL Server with "Allow Nulls" unchecked. I have
no idea what I may have done to cause this (I assume I did something, since
such changes are rarely truly spontaneous!), but I have no idea what it may
have been.

Any ideas?

Thanks in advance for your help.

 

[Sylvain Lafontaine]

A default value such as 0 or "" can take the place of a Not Null property;
so I would say that you have added a default value or set a string field to
be allowed to have a zero length.

Also, I'm not sure if you have the right method of learning how to work with
SQL-Server. If you want to use SQL-Server as the backend, then you should
work directly on the sql-server and not on Access for developing your data
structure.

Finally, this newsgroup is about ADP and SQL-Server and not about Upsising
or ODBC linked tables; so you should ask in a more appropriate newsgroup
like m.p.access.upsizing .

 

[Guest]

Thanks Sylvain,

Last thing first: Perhaps it was because of how I was accessing this forum
through the ms Discussion Groups site, but I could not find what appeared to
be a more appropriate group (I still don't see m.p.access.upsizing!). Sorry
for the mis-post.

Anyway, I haven't changed any default values to 0 or "", so that can't be
the explanation why something changed. In any case, in part because of
running into this "What Changed?" problem, I was already coming around to the
idea of working on the data structure in SQL Server not Access. But I'd
still like to know what happened...thanks for your input and ideas.

Ed

 

[Norman Yuan]

I'd not bother if the "required" field in Jet database is changed to "Allow
NULL" or not. Since Jet database and SQL Server are two different type
database engine and there are quite some differences, such as data types, it
is almost guranteed that the "Upsizing Wizard" would leave something
converted not so well. So, it almost always necessary, after the upsizing,
you still need to go through each table in SQL Server to do necessary
midifications, such as Access's "memo" would be changed to "ntext", but most
likely you'd like use "navrchar" instead, you may also want to add/set/check
primary key/index... If you do not do this and completely rely on the
"Upsizing Wizard", your new SQL Server database is unlikely optimized.

 

[Sylvain Lafontaine]

Oups, sorry, it's not upsizing but sqlupsizing. Personally, I don't care
for the mis-post, it's for you; as you have a better chance to get a correct
answer by posting to the most relevant newgroup as possible.

 

[Tom Wimpernark]

why would anyone want to use nvarchar?

we use varchar over here; because we have a modern language!

maybe you kids in china should stop bickering and learn a real language like
english!

 

[Robert Morley]

Go away, Aaron...you're not welcome here. (And with the extra time you have
from not posting here, maybe you can learn some culture, and that English
*isn't* the only language in the world, nor is it even a *good* language,
from a linguistic standpoint!)



Rob