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 8 1609
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.
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.
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.
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.
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
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
"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!
"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! This thread has been closed and replies have been disabled. Please start a new discussion. Similar topics
by: Gary Bouchard |
last post by:
I have a Visual Basic 6 application that uses MDB or SQL Server
databases.
I was wondering if it was possible via Automation or ADO or some
method, where I could programmicatlly upsize an MDB...
|
by: Big Time |
last post by:
I have an Access 2000 DB that I've been considering upsizing to SQL Server
2K. I'm wondering if anyone can share their experiences in upsizing and let
me know of any tips or pratfalls. I've been...
|
by: Bon |
last post by:
Hello All
I got "Tables are skipped or export failed" error when I used upsizing
wizard on migrating MS Access 2000 to MS SQL Server 2000.
I am changing my application backend database from MS...
|
by: Calum Chisholm |
last post by:
I'm looking to call the upsizing wizard from within a VBA function,
preferably automating the entire upsizing process. Has anyone achieved
this under Access 2003?
The best I've managed so far is...
|
by: Big Time |
last post by:
I have an Access 2000 DB that I've been considering upsizing to SQL Server
2K. I'm wondering if anyone can share their experiences in upsizing and let
me know of any tips or pratfalls. I've been...
|
by: John |
last post by:
Hi
We have a front end/back end type access app. We would like to upsize the
app to sql server but can not re-write the whole app immediately. Is it
feasible to just upsize the backend (data...
|
by: Devonish |
last post by:
I am planning to convert an existing Access database which has a back
end
(data tables and relationships only) on a server and a copy of the front
end
(form, queries, reports) on each of about a...
|
by: JM |
last post by:
I'm using Access 2003 to attempt an upsize to SQL Server 2000. The
Upsizing Wizard is giving me tons of problems with error messages like:
1. "Object is invalid. Extended properties not...
|
by: Jim Devenish |
last post by:
I am continuing my exploration about upsizing to SQLServer from Access
2000.
I have a split database with a front-end and a back-end, each of which
is A2K. I have spent some time in bookshops...
|
by: Wayne |
last post by:
I've just installed SQL Server 2005 Express together with SQL
Management Studio Express on my local machine and I'm trying to upsize
a data mdb to SQL Server using the upsizing wizard. The data...
|
by: CloudSolutions |
last post by:
Introduction:
For many beginners and individual users, requiring a credit card and email registration may pose a barrier when starting to use cloud servers. However, some cloud server providers now...
|
by: Faith0G |
last post by:
I am starting a new it consulting business and it's been a while since I setup a new website. Is wordpress still the best web based software for hosting a 5 page website? The webpages will be...
|
by: isladogs |
last post by:
The next Access Europe User Group meeting will be on Wednesday 3 Apr 2024 starting at 18:00 UK time (6PM UTC+1) and finishing by 19:30 (7.30PM).
In this session, we are pleased to welcome former...
|
by: ryjfgjl |
last post by:
In our work, we often need to import Excel data into databases (such as MySQL, SQL Server, Oracle) for data analysis and processing. Usually, we use database tools like Navicat or the Excel import...
|
by: taylorcarr |
last post by:
A Canon printer is a smart device known for being advanced, efficient, and reliable. It is designed for home, office, and hybrid workspace use and can also be used for a variety of purposes. However,...
|
by: ryjfgjl |
last post by:
If we have dozens or hundreds of excel to import into the database, if we use the excel import function provided by database editors such as navicat, it will be extremely tedious and time-consuming...
|
by: emmanuelkatto |
last post by:
Hi All, I am Emmanuel katto from Uganda. I want to ask what challenges you've faced while migrating a website to cloud.
Please let me know.
Thanks!
Emmanuel
|
by: nemocccc |
last post by:
hello, everyone, I want to develop a software for my android phone for daily needs, any suggestions?
|
by: Sonnysonu |
last post by:
This is the data of csv file
1 2 3
1 2 3
1 2 3
1 2 3
2 3
2 3
3
the lengths should be different i have to store the data by column-wise with in the specific length.
suppose the i have to...
| |