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  1622 
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************* *********@o13g2 00...legr 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).
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************* *********@o13g2 00...legr 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).
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.goo glegroups.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.goo glegroups.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 database to SQL
Server.
I can run the upsizing wizard from within Access to do the upsizing,
and the database converts fine.
|
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 playing around with the upsize
wizard however not all of my tables have properly converted. None of the
primary keys transfer (I understand this is a limitation) and the whole
thing hasn't really worked the way I thought it would. I have tried...
|
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 Access 2000 to MS
SQL Server 2000. My front end is MS Access interface. When I used the
MS Access 2000's Upsizing Wizard for database migration, some tables
cannot be migrated. The upsizing wizard report states some tables are
"Tables are...
|
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 to .Execute its CommandBar control, but
this is a pretty messy approach and still requires input on the part
of the user.
Anyone know of a direct function call similar to those detailed at
http://www.mvps.org/access/general/gen0028.htm?
|
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 playing around with the upsize
wizard however not all of my tables have properly converted. None of the
primary keys transfer (I understand this is a limitation) and the whole
thing hasn't really worked the way I thought it would. I have tried...
| | |
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 part) only to sql server using
upsizing wizard without any drastic effect on the performance of the front
end access app (which would link to the tables on the sql server after
upsizing)?
Thanks
|
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 dozen workstations.
I intend to convert the back end to SqlServer and wish to use the
upsizing
wizard. I am acquiring SSW Upsizing Pro! 2000 which seems to be
recommended in other discussions.
|
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 permitted on . . ."
2. "No primary or candidate keys in referenced table . . . that match
referencing column list in foreign key . . . Could not create
constraint.
3. "Incorrect syntax near . . . " (When trying to upsize queries.)
|
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 trying to learn about the
way forward and trying to decide which to buy. The bit I am interested
in is usually at page 900 and I am not sure whether I want to buy the
first 800.
It appears that upsizing creates an Access project as the...
|
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 mdb is
also on my local machine. I've been at it for a couple of hours now
and I keep getting the same error despite trying everything I can
think of:
Connection failed:
SQLState: '01000'
SQL Server Error: 2
|
by: Hystou |
last post by:
Most computers default to English, but sometimes we require a different language, especially when relocating. Forgot to request a specific language before your computer shipped? No problem! You can effortlessly switch the default language on Windows 10 without reinstalling. I'll walk you through it.
First, let's disable language synchronization. With a Microsoft account, language settings sync across devices. To prevent any complications,...
| | |
by: jinu1996 |
last post by:
In today's digital age, having a compelling online presence is paramount for businesses aiming to thrive in a competitive landscape. At the heart of this digital strategy lies an intricately woven tapestry of website design and digital marketing. It's not merely about having a website; it's about crafting an immersive digital experience that captivates audiences and drives business growth.
The Art of Business Website Design
Your website is...
|
by: Hystou |
last post by:
Overview:
Windows 11 and 10 have less user interface control over operating system update behaviour than previous versions of Windows. In Windows 11 and 10, there is no way to turn off the Windows Update option using the Control Panel or Settings app; it automatically checks for updates and installs any it finds, whether you like it or not. For most users, this new feature is actually very convenient. If you want to control the update process,...
|
by: tracyyun |
last post by:
Dear forum friends,
With the development of smart home technology, a variety of wireless communication protocols have appeared on the market, such as Zigbee, Z-Wave, Wi-Fi, Bluetooth, etc. Each protocol has its own unique characteristics and advantages, but as a user who is planning to build a smart home system, I am a bit confused by the choice of these technologies. I'm particularly interested in Zigbee because I've heard it does some...
|
by: isladogs |
last post by:
The next Access Europe User Group meeting will be on Wednesday 1 May 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 a new presenter, Adolph Dupré who will be discussing some powerful techniques for using class modules.
He will explain when you may want to use classes instead of User Defined Types (UDT). For example, to manage the data in unbound forms.
Adolph will...
|
by: conductexam |
last post by:
I have .net C# application in which I am extracting data from word file and save it in database particularly. To store word all data as it is I am converting the whole word file firstly in HTML and then checking html paragraph one by one.
At the time of converting from word file to html my equations which are in the word document file was convert into image.
Globals.ThisAddIn.Application.ActiveDocument.Select();...
|
by: TSSRALBI |
last post by:
Hello
I'm a network technician in training and I need your help.
I am currently learning how to create and manage the different types of VPNs and I have a question about LAN-to-LAN VPNs.
The last exercise I practiced was to create a LAN-to-LAN VPN between two Pfsense firewalls, by using IPSEC protocols.
I succeeded, with both firewalls in the same network. But I'm wondering if it's possible to do the same thing, with 2 Pfsense firewalls...
| | |
by: muto222 |
last post by:
How can i add a mobile payment intergratation into php mysql website.
|
by: bsmnconsultancy |
last post by:
In today's digital era, a well-designed website is crucial for businesses looking to succeed. Whether you're a small business owner or a large corporation in Toronto, having a strong online presence can significantly impact your brand's success. BSMN Consultancy, a leader in Website Development in Toronto offers valuable insights into creating effective websites that not only look great but also perform exceptionally well. In this comprehensive...
| |
