Home All Groups Group Topic Archive Search About

MOVING FROM ACCESS TO SQL

Author
18 Mar 2006 10:06 AM
alami_marieme@hotmail.com
Hi
could anyone help please...I've problems moving my database from Access
to SQL specially with tables relationships...Here is the probl:I have a
form having the Order number, order date, client code...this
information is taken from table BLA.on the same form,I've a subform
having quantity bought,label of what has been bought,unit price,and
total price.This information is taken from table SBLA.NOW under
Access,I fill the order number, order date,client code and once I enter
quantity bought a row is automatically added in SBLA with an auto
number (primary key) and at the same moment a table is opened to show
the arrivals to pick up what I need.WITH SQL,no autonumber is generated
and no row is automatically added meaning the table arrival is not
shown but once I click on save the row is then added but unfortunately
I have no more access to the table arrival...Please keep in mind that
I've a lot of code behind that manages all these procedures.
Could anyone help pleeaaaaaaaase I decided to migrate to SQL to make my
life easy since Access and SQL are both microsoft products BUT ....
thanks a lot

Author
18 Mar 2006 11:55 AM
David Portas
alami_mari***@hotmail.com wrote:
Show quote
> Hi
> could anyone help please...I've problems moving my database from Access
> to SQL specially with tables relationships...Here is the probl:I have a
> form having the Order number, order date, client code...this
> information is taken from table BLA.on the same form,I've a subform
> having quantity bought,label of what has been bought,unit price,and
> total price.This information is taken from table SBLA.NOW under
> Access,I fill the order number, order date,client code and once I enter
> quantity bought a row is automatically added in SBLA with an auto
> number (primary key) and at the same moment a table is opened to show
> the arrivals to pick up what I need.WITH SQL,no autonumber is generated
> and no row is automatically added meaning the table arrival is not
> shown but once I click on save the row is then added but unfortunately
> I have no more access to the table arrival...Please keep in mind that
> I've a lot of code behind that manages all these procedures.
> Could anyone help pleeaaaaaaaase I decided to migrate to SQL to make my
> life easy since Access and SQL are both microsoft products BUT ....
> thanks a lot

SQL Server is not Access! Reading this and your previous posts it seems
like you need to step back and think about what you are trying to
achieve. You simply cannot expect to use SQL Server in the same way you
program a desktop database like Access.

What are your goals in upgrading to SQL Server? If you want your
application to scale then you should really plan to redesign and
rewrite using SQL stored procedures. That may involve some considerable
development effort but if you aren't prepared to invest that time now
then it may be better to wait until you can justify doing the necessary
work.

--
David Portas, SQL Server MVP

Whenever possible please post enough code to reproduce your problem.
Including CREATE TABLE and INSERT statements usually helps.
State what version of SQL Server you are using and specify the content
of any error messages.

SQL Server Books Online:
http://msdn2.microsoft.com/library/ms130214(en-US,SQL.90).aspx
--
Author
18 Mar 2006 4:22 PM
alami_marieme@hotmail.com
I know that using SQL requires some efforts...what i'm looking for is
reliability and speed...For the SQL version i'm using, it's SQL server
7.0.
Have you really understood the prob I'm facing actually?
regards
Author
18 Mar 2006 9:08 PM
David Portas
alami_mari***@hotmail.com wrote:
> I know that using SQL requires some efforts...what i'm looking for is
> reliability and speed...For the SQL version i'm using, it's SQL server
> 7.0.
> Have you really understood the prob I'm facing actually?
> regards

Create a stored procedure to add new orders. You can insert whatever
rows and values you need with a proc. If you need help with that then
post DDL for the table(s) and show us what end result you want. See the
following article which describes the best way to post a problem here:

http://www.aspfaq.com/etiquette.asp?id=5006

--
David Portas, SQL Server MVP

Whenever possible please post enough code to reproduce your problem.
Including CREATE TABLE and INSERT statements usually helps.
State what version of SQL Server you are using and specify the content
of any error messages.

SQL Server Books Online:
http://msdn2.microsoft.com/library/ms130214(en-US,SQL.90).aspx
--
Author
18 Mar 2006 6:16 PM
PhilEnd
Hi,
If you're really committed to do the switch then you should consider to
change totally the way you work in Access.

1st, forget the use of .MDB and move to .ADP (Access Data Project),
it's faster, more stable, you will have a better security of your
data and you will reduce drastically the traffic load on you LAN, but
it 's a complete new way to work with Access.

2nd, you will need a deep understanding of SQL and its programming
using VIEWs and stored PROCs.

Finally you will end up using Access only as the front end for the
"acquisition" (manual entry) and the "presentation" (on screen
and report) of your data, but most of the "business" logic will
reside on the SQL server.

I can tell you, it's not an easy task and it will take you several
months to master it, but the result worth the effort.

I have been doing just that for the past 18 months and it starts to pay
now.

Cheers.

Phil.

AddThis Social Bookmark Button