By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
424,466 Members | 1,588 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 424,466 IT Pros & Developers. It's quick & easy.

Upsizing MDB to SQL server

P: n/a
Hi everybody,

I try to migrate my Access 2003 MDB BackEnd (with data) to SQL server (MSDE
8.0) with the Access Wizard, but when i finish, all my table with a random
autonumber primarykey have no record, and i was not able to add record ??

I try to change random field to a simple autonumber (in MDB) but it's
impossible :-(

I try too SSW upsizing Pro software, but i have the same problem.
Thank's for help !

Indrid


Nov 13 '05 #1
Share this Question
Share on Google+
8 Replies


P: n/a
Did you know that there are those of us who never use (knowingly) a
wizard for anything? My experience is that wizards won't do what we
want, won't do it well, or will add some goodies of its own that we
don't want. More often than not, wizards produce a combination of the
three.
(They also deceive those who don't know Access into thinking that they
do, but this is another story).
My suggestion is that you create your tables and relationships in MSDE
using the diagram designer and then inport your JET/MDB data to these.
Assuming you have queries, do a text cut and paste of these to stored
procedures, views or udfs as appropriate. When you try to save them,
you will be advised if there are errors and have a chance to correct
them.
This may be a lot of work but it's nothing comparted with the work one
might find in two months when one discovers how the Wizard really did
things.
Another advantage of this is that one may learn a bit about MS-SQL in
doing it. Using MS_SQL (even MSDE) is a big waste if we do not discover
its strangths and advantages and use them.
MS-SQL is not JET. It will never be JET.

Nov 13 '05 #2

P: n/a
Did you know that there are those of us who never use (knowingly) a
wizard for anything? My experience is that wizards won't do what we
want, won't do it well, or will add some goodies of its own that we
don't want. More often than not, wizards produce a combination of the
three.
(They also deceive those who don't know Access into thinking that they
do, but this is another story).
My suggestion is that you create your tables and relationships in MSDE
using the diagram designer and then inport your JET/MDB data to these.
Assuming you have queries, do a text cut and paste of these to stored
procedures, views or udfs as appropriate. When you try to save them,
you will be advised if there are errors and have a chance to correct
them.
This may be a lot of work but it's nothing comparted with the work one
might find in two months when one discovers how the Wizard really did
things.
Another advantage of this is that one may learn a bit about MS-SQL in
doing it. Using MS_SQL (even MSDE) is a big waste if we do not discover
its strangths and advantages and use them.
MS-SQL is not JET. It will never be JET.

Nov 13 '05 #3

P: n/a
Thank's for reply,

I think it's a good idea to use MSDE to upsize my MDB, i create a script (i
must modify after for my autonumber) of my mdb and after, i have importing
my data, and all work fine.
Indrid


"lylefair" <ly******@yahoo.ca> a écrit dans le message de news:
11**********************@o13g2000cwo.googlegroups. com...
Did you know that there are those of us who never use (knowingly) a
wizard for anything? My experience is that wizards won't do what we
want, won't do it well, or will add some goodies of its own that we
don't want. More often than not, wizards produce a combination of the
three.
(They also deceive those who don't know Access into thinking that they
do, but this is another story).
My suggestion is that you create your tables and relationships in MSDE
using the diagram designer and then inport your JET/MDB data to these.
Assuming you have queries, do a text cut and paste of these to stored
procedures, views or udfs as appropriate. When you try to save them,
you will be advised if there are errors and have a chance to correct
them.
This may be a lot of work but it's nothing comparted with the work one
might find in two months when one discovers how the Wizard really did
things.
Another advantage of this is that one may learn a bit about MS-SQL in
doing it. Using MS_SQL (even MSDE) is a big waste if we do not discover
its strangths and advantages and use them.
MS-SQL is not JET. It will never be JET.

Nov 13 '05 #4

P: n/a
Thank's for reply,

I think it's a good idea to use MSDE to upsize my MDB, i create a script (i
must modify after for my autonumber) of my mdb and after, i have importing
my data, and all work fine.
Indrid


"lylefair" <ly******@yahoo.ca> a écrit dans le message de news:
11**********************@o13g2000cwo.googlegroups. com...
Did you know that there are those of us who never use (knowingly) a
wizard for anything? My experience is that wizards won't do what we
want, won't do it well, or will add some goodies of its own that we
don't want. More often than not, wizards produce a combination of the
three.
(They also deceive those who don't know Access into thinking that they
do, but this is another story).
My suggestion is that you create your tables and relationships in MSDE
using the diagram designer and then inport your JET/MDB data to these.
Assuming you have queries, do a text cut and paste of these to stored
procedures, views or udfs as appropriate. When you try to save them,
you will be advised if there are errors and have a chance to correct
them.
This may be a lot of work but it's nothing comparted with the work one
might find in two months when one discovers how the Wizard really did
things.
Another advantage of this is that one may learn a bit about MS-SQL in
doing it. Using MS_SQL (even MSDE) is a big waste if we do not discover
its strangths and advantages and use them.
MS-SQL is not JET. It will never be JET.

Nov 13 '05 #5

P: n/a
Br
lylefair <ly******@yahoo.ca> wrote:
Did you know that there are those of us who never use (knowingly) a
wizard for anything?
Amen to that!
My experience is that wizards won't do what we
want, won't do it well, or will add some goodies of its own that we
don't want. More often than not, wizards produce a combination of the
three.
(They also deceive those who don't know Access into thinking that they
do, but this is another story).
Hehe.
My suggestion is that you create your tables and relationships in MSDE
using the diagram designer and then inport your JET/MDB data to these.
Assuming you have queries, do a text cut and paste of these to stored
procedures, views or udfs as appropriate. When you try to save them,
you will be advised if there are errors and have a chance to correct
them.
This may be a lot of work but it's nothing comparted with the work one
might find in two months when one discovers how the Wizard really did
things.
Another advantage of this is that one may learn a bit about MS-SQL in
doing it. Using MS_SQL (even MSDE) is a big waste if we do not
discover its strangths and advantages and use them.
MS-SQL is not JET. It will never be JET.


We ended up redesigning our apps to ADPs. There are downsides in that
now we have to maintain two versions and ADPs require a number of tricks
to work so you can update data... but there are also many benefits in
redesigning it to use store procedures etc and putting the core data
processing logic on the server.
--
regards,

Bradley

A Christian Response
http://www.pastornet.net.au/response
Nov 13 '05 #6

P: n/a
Br
lylefair <ly******@yahoo.ca> wrote:
Did you know that there are those of us who never use (knowingly) a
wizard for anything?
Amen to that!
My experience is that wizards won't do what we
want, won't do it well, or will add some goodies of its own that we
don't want. More often than not, wizards produce a combination of the
three.
(They also deceive those who don't know Access into thinking that they
do, but this is another story).
Hehe.
My suggestion is that you create your tables and relationships in MSDE
using the diagram designer and then inport your JET/MDB data to these.
Assuming you have queries, do a text cut and paste of these to stored
procedures, views or udfs as appropriate. When you try to save them,
you will be advised if there are errors and have a chance to correct
them.
This may be a lot of work but it's nothing comparted with the work one
might find in two months when one discovers how the Wizard really did
things.
Another advantage of this is that one may learn a bit about MS-SQL in
doing it. Using MS_SQL (even MSDE) is a big waste if we do not
discover its strangths and advantages and use them.
MS-SQL is not JET. It will never be JET.


We ended up redesigning our apps to ADPs. There are downsides in that
now we have to maintain two versions and ADPs require a number of tricks
to work so you can update data... but there are also many benefits in
redesigning it to use store procedures etc and putting the core data
processing logic on the server.
--
regards,

Bradley

A Christian Response
http://www.pastornet.net.au/response
Nov 13 '05 #7

P: n/a

"lylefair" <ly******@yahoo.ca> wrote in message
news:11**********************@o13g2000cwo.googlegr oups.com...
Did you know that there are those of us who never use (knowingly) a
wizard for anything? My experience is that wizards won't do what we
want, won't do it well, or will add some goodies of its own that we
don't want. More often than not, wizards produce a combination of the
three.
(They also deceive those who don't know Access into thinking that they
do, but this is another story).

YES! I was deceived by a Wizard once also!
My suggestion is that you create your tables and relationships in MSDE
using the diagram designer and then inport your JET/MDB data to these.
Assuming you have queries, do a text cut and paste of these to stored
procedures, views or udfs as appropriate. When you try to save them,
you will be advised if there are errors and have a chance to correct
them.
This may be a lot of work but it's nothing comparted with the work one
might find in two months when one discovers how the Wizard really did
things.
Another advantage of this is that one may learn a bit about MS-SQL in
doing it. Using MS_SQL (even MSDE) is a big waste if we do not discover
its strangths and advantages and use them.
MS-SQL is not JET. It will never be JET.

ALSO--Consider the work involved when one starts to use one in one's
sentences!
Nov 13 '05 #8

P: n/a

"lylefair" <ly******@yahoo.ca> wrote in message
news:11**********************@o13g2000cwo.googlegr oups.com...
Did you know that there are those of us who never use (knowingly) a
wizard for anything? My experience is that wizards won't do what we
want, won't do it well, or will add some goodies of its own that we
don't want. More often than not, wizards produce a combination of the
three.
(They also deceive those who don't know Access into thinking that they
do, but this is another story).

YES! I was deceived by a Wizard once also!
My suggestion is that you create your tables and relationships in MSDE
using the diagram designer and then inport your JET/MDB data to these.
Assuming you have queries, do a text cut and paste of these to stored
procedures, views or udfs as appropriate. When you try to save them,
you will be advised if there are errors and have a chance to correct
them.
This may be a lot of work but it's nothing comparted with the work one
might find in two months when one discovers how the Wizard really did
things.
Another advantage of this is that one may learn a bit about MS-SQL in
doing it. Using MS_SQL (even MSDE) is a big waste if we do not discover
its strangths and advantages and use them.
MS-SQL is not JET. It will never be JET.

ALSO--Consider the work involved when one starts to use one in one's
sentences!
Nov 13 '05 #9

This discussion thread is closed

Replies have been disabled for this discussion.