Qstion abt choosing btwn ADP and MDB when upsizing to SQL *952008

[J.Alladien]

Good day to ALL,

Am right now exploring SQL and very new to it ,so have some questions:

1.When upsizing to SQL what would be better as a Front End a ADP file or a
MDB file and why?
2.I noticed that the UPSizing wizard does not take care of all the work,
some of it you have to do manually, but before I do that :IS there a way to
upsize where there are even less conversion errors then the wizard itself,
if there is I would not have to do unnecesseary work for that!

Thanks in advance for all the good advice I ve always got from this forum!

 

[Albert D. Kallal]

Good day to ALL,

Am right now exploring SQL and very new to it ,so have some questions:

1.When upsizing to SQL what would be better as a Front End a ADP file or a
MDB file and why?

If you're creating an application from scratch, and your intention to is to
use it with SQL server, then you certainly could consider using an ADP and
start developing with that.

However if you have an existing application, then the choice gets a little
bit more difficult. The reason why it gets more difficult is because if you
have a lot of code and events in your application and you used "dao" code,
then that code will have to be rewritten to use the "ado" object model. In
other words if you have an application with a lot of forms and code already,
I suggest you avoid using an adp project since a lot of code could wind up
with the requirement to be changed.

So, if you are using the dao object model for recordset code, then I would
stick with a front end mdb. If you have little or no code at all in your
application, then a access project is a reasonable choice.

So the answer's is not really one way or the other, it depends on the status
of your particular application that you have now.

2.I noticed that the UPSizing wizard does not take care of all the work,
some of it you have to do manually, but before I do that :IS there a way
to
upsize where there are even less conversion errors then the wizard
itself,
if there is I would not have to do unnecesseary work for that!

You'll have to explain to me what kind of errors you are talking about? Are
you talking about data conversion errors? Or problems with forms and code
that don't work correctly after you upsized? Keep in mind the upsizing
wizard does NOT modify your application "code" for you, it simply allows you
to move data to SQL server, end of story. I don't see why you would have
problems moving the data, it should upload quite nice. (ensuring that all
your forms and code is in working order after the upload of data is a whole
other issue here).

And, if your application was already split then again you find it easier to
simply upgrade the backend data part to sql server.

So, for most existing applications, it's better to keep your code and
application as is, and simply link the tables to SQL server (you really
should ensure that all of your tables have a primary key, and I do suggest
that you at a time stamp to all fields, the wizard will do this for you
also).

For the most part about 99% of your code should run "as is" if you keep
things as a mdb and link to sql server.

 

[J.Alladien]

Ok,

Explanation was very clear, so I think I understand,but still have a quesion,

As I very often need to make changes to the BE of my applications due to new
requirements of users,where is that easier to do, my gues would be in the ADP
file ,or is that not true,please keep in mind that I know very little of SQL
and ADP, I due however know a bit about MDB's, but then again I noticed that
if I need to make changes to the BE of the MDB I would have to do it in
SQL,or is this not so!

So what would your advise be to me:
1.Learn how to work with SQL and ADP( which I could do I guess)
2.continue working with MDB, but then how can I easily modify my BE when
needed?

my appoligies if I have stated some stupid questions, but this is because I
have very little experience with ADP and SQL!

Thanks in advance for your advice!