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

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

"Tom Wimpernark" <Tom_Wimpernark@xxxxxxxxxxx> wrote in message
news:u$xHkMtoHHA.4428@xxxxxxxxxxxxxxxxxxxxxxx
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!



"Norman Yuan" <NotReal@xxxxxxxxxxx> wrote in message
news:eX%23A9lVoHHA.4032@xxxxxxxxxxxxxxxxxxxxxxx
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.


"Ed B" <EdB@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:5EE8196D-95F9-4A72-85BD-D1C0A3EA2D30@xxxxxxxxxxxxxxxx
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.





.

Relevant Pages

  • Re: Upsize no longer transfers "Required" fields to Not "Allow Nulls"
    ... because we have a modern language! ... 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. ... I have been working on upsizing an Access 2000 data structure to SQL Server ...
    (microsoft.public.access.adp.sqlserver)
  • Re: Upsize no longer transfers "Required" fields to Not "Allow Nulls"
    ... I'd not bother if the "required" field in Jet database is changed to "Allow ... Since Jet database and SQL Server are two different type ... So, it almost always necessary, after the upsizing, ... I have been working on upsizing an Access 2000 data structure to SQL ...
    (microsoft.public.access.adp.sqlserver)
  • Re: Access 2002 Upsizing Wizard does not copy forms
    ... Upsizing *.mdb to SQL Server, using Upsizing Wizard, ONLY transfer data from ... Jet database to a SQL Server database (either new or existing, ...
    (microsoft.public.access.adp.sqlserver)
  • Re: Upsize no longer transfers "Required" fields to Not "Allow Nul
    ... Sylvain Lafontaine, ing. ... If you want to use SQL-Server as the backend, ... I have been working on upsizing an Access 2000 data structure to SQL ...
    (microsoft.public.access.adp.sqlserver)
  • RE: Access limitations/suitablity
    ... Sorry for my delayed response. ... I think Tony has some great thoughts on upsizing as to when and how. ... Dave Hargis, Microsoft Access MVP ... performance they had to convert to something like SQL Server? ...
    (microsoft.public.access.gettingstarted)