Everything I Always Did With Access

  • Thread starter Thread starter Brian Smither
  • Start date Start date
B

Brian Smither

I'm trying out how I used to do things with Access, but now as the ADP
front to a SSE.

One such task was to search and replace for anything in a particular column
and replace it with NULL throughout the entire record set. I tried that
today. I recommend against it.

Yes, I will be reading up on the T-SQL language to see how I can do that
quickly and efficiently (maybe even make a SP out of it).

But, is there a well-respected book that exists which has a title something
like: Everything You Always Did Access But Now Can't Figure Out to Do It in
SS"?
 
Since MS is not moving forward with the ADP type project, I would
stick to Access MDBs.

UPDATE YourTable
SET YourColumn = NULL
WHERE YourColumn LIKE '%SearchText%'

is the syntax to accomplish what you are wanting to do.

Robert
 
If you want to work with SQL-Server, the first thing to do would be to learn
more about SQL-Server itself and the language it uses (T-SQL). This is true
not only for ADP but for any other interface working with SQL-Server (ie.,
MDB/ACCDB databases with ODBC linked tables and passthrough queries, ASP,
ASP.NET, .NET technologies, etc., etc.) and will remains true in the future.
You don't need a book about ADP and T-SQL for this.

The second thing would be to learn a little more about ADO. However and
contrary to SQL-Server, don't push this knowledge to far as ADO - like ADP
and other technologies based on COM/DCOM like VBA - is in the process of
being slowly deprecated by MS in order to be replaced with .NET. This
doesn't mean that ADP, ADO or VBA will be removed from the next Office
platform; it means that you shouldn't expect any real new features in the
future for any of these technologies and that you should start thinking
about .NET if you want to integrate any new features in the future or have a
better integration with these current little things like a better support
for images, graphs, web services, notification services, transactions,
disconnected services, etc.

You should now see ADP, ADO, VBA and COM/DCOM/ActiveX as a static platform
that will not evolve any more. We could probably say the same with DAO and
the ODBC linked tables. In Access 2007, there have been some little
ameliorations to DAO, like support for multi-values fields and a few other
features. However, these features are mainly related to a better support
for Sharepoint and are practically of no interest to you if you are not
interested in Sharepoint. (Excerpt maybe for the multi-valued fields but
using these would be like opening a little Pandora's box in my opinion.).
If possible that in the future, some other features will be added to DAO
(like they have done with Office 2007); however, in comparaison to .NET,
probably that these will be little features and not real big new stuff.

For the rest, I would suggest that you take a look at the previous messages
posted in this newsgroup in the past. Probably that you will find a lot of
useful things to know about ADP.
 
Back
Top