Re: Should I worry that my Access to SQL conversion has gone so well?
- From: "Albert D. Kallal" <PleaseNOOOsPAMmkallal@xxxxxxx>
- Date: Wed, 2 Aug 2006 13:20:26 -0600
You got some good comments, and I will add a few more:
Your sub form editing problems will likely go away if you make sure that
ALL tables have a primary key, and also have a time stamp field. These
fields need to be exposed to the access form (and sub-form). When you do
this, you should get your editing, and adding ability back (access uses the
time stamp field to figure out what has been changed..and if no timestamp
field..it looks at all of the fields.....and makes life difficult for
ms-access). In fact, you don't usually even have to change your
forms/sub-forms from the tables to queries..but, you do need to have the pk
+ timestamp field exposed for smooth operations...
the above apples to most forms....they need that time stamp AND a PK field
exposed. This will ensure smooth editing from ms-access.
Should I be worried??? It seems too easy. Have I gained anything my
moving from an Access back end to SQL in this way?
Well, if you needed to move to sql server, then the above is a good gain. IF
you did not need to move to sql server, the you gain nothing (except a more
time consuming sql server system to maintain in addition to your software).
Unless your software is multi-user, and has a heavy load of many users, then
sql is not always needed. I mean, with 10 users on a cheap office network,
ms-access will absolute scream in terms of performance. However, sql server
is more reliable, and does not suffer from corruptions like a JET based
appcation can. Further, sql server can scale to more users with more
reliability. So, did you gain?...well, only you can answer this, and that
answer is going to depend on your given situation.
However, moving a stand alone JET based appcation to sql server will most
certainly run slower then a JET based one. Often, the JET will run about two
times as fast as a sql based application (same machine, same hardware).
Before I started I
was given all kinds of dire warnings about having to re-write my front
end in VB.NET. Why was it so easy??? Something nasty must be waiting
around the corner. Any suggestions what it might be?
There is no big deal here. Only those people with their noses high in the
air that look down on ms-access think that you must use sql server for
everything, and that the JET database engine with ms-access is a toy.
However, what is really nice is that at the end of the day, ms-access is
great front end to sql server.
--
Albert D. Kallal
Edmonton, Alberta Canada
pleaseNOOSpamKallal@xxxxxxx
Bobby
.
- Follow-Ups:
- References:
- Prev by Date: Re: Converting Access 97 - Acess2003/VB 6.0
- Next by Date: Re: Should I worry that my Access to SQL conversion has gone so well?
- Previous by thread: Re: Should I worry that my Access to SQL conversion has gone so well?
- Next by thread: Re: Should I worry that my Access to SQL conversion has gone so well?
- Index(es):
Relevant Pages
|
