RE: [aus-dotnet] Microsoft.Jet.OLEDB.4.0

[Sean Malloy]

Title: RE: [aus-dotnet] Microsoft.Jet.OLEDB.4.0

A couple of ways..

 

UPDATE Table1 SET [ThisName] = Table2.[ThatName]  FROM Table1 INNER JOIN Table2 ON Table1.RecId = Table2.RecId

WHERE Table1.RecId = Table2.RecId

 

Or using a subquery (I have no idea how this might perform!)

 

UPDATE Table1 SET Table1.ThisName = (SELECT TOP 1 ThatName FROM Table2 WHER Table2.RecId = Table1.RecId)

 

 

-----Original Message-----
From: Phil Best [mailto:Phil@xxxxxxxxxxxxxxxxxx]
Sent: Friday, 3 December 2004 15:33
To: dotnet@xxxxxxxxxxx
Subject: RE: [aus-dotnet] Microsoft.Jet.OLEDB.4.0

Hi Michael, I need something like this...   update Table1 set ThisName = Table2.ThatName from Table2 where Table1.RecId = Table2.RecId   any ideas??   regards, Phil.

-----Original Message-----
From: Michael Sim [mailto:dotnet-owner@xxxxxxxxxxx]On Behalf Of Michael Sim
Sent: Friday, 3 December 2004 2:16 PM
To: dotnet@xxxxxxxxxxx
Subject: RE: [aus-dotnet] Microsoft.Jet.OLEDB.4.0

Same as for SQL   Update tbl.... Insert into...

---

From: dotnet-owner@xxxxxxxxxxx on behalf of Phil Best
Sent: Fri 3/12/2004 3:18 PM
To: dotnet@xxxxxxxxxxx
Subject: RE: [aus-dotnet] Microsoft.Jet.OLEDB.4.0

Hi again,

Any idea how to do an Update from??

is it even possible??

Phil.

-----Original Message-----
From: dotnet-owner@xxxxxxxxxxx [mailto:dotnet-owner@xxxxxxxxxxx]On
Behalf Of Ken Schaefer
Sent: Friday, 3 December 2004 11:10 AM
To: dotnet@xxxxxxxxxxx
Subject: RE: [aus-dotnet] Microsoft.Jet.OLEDB.4.0


Jet SQL, for the most part, is the same as ANSI SQL. The main trick is
JOINs,
which need to have ( )

Cheers
Ken

: -----Original Message-----
: From: dotnet-owner@xxxxxxxxxxx [mailto:dotnet-owner@xxxxxxxxxxx] On Behalf
Of
: Greg Low
: Sent: Friday, 3 December 2004 12:07 PM
: To: dotnet@xxxxxxxxxxx
: Subject: RE: [aus-dotnet] Microsoft.Jet.OLEDB.4.0
:
: Hi Phil,
:
: Looks pretty close but sections of connection strings are separated by
: semicolons, not commas. An example from www.connectionstrings.com is:
:
: "Provider=Microsoft.Jet.OLEDB.4.0;Data Source=\somepath\mydb.mdb;User
: Id=admin;Password=;"
:
: It's speaks "Access" brand of SQL, which isn't really like any other
: variant. Easiest way to get started on queries is to use a copy of
: Access and build up a query in the query designer. Helps avoid learning
: its quirks.
:
: Regards,
:
: Greg
:
:
: -----Original Message-----
: From: dotnet-owner@xxxxxxxxxxx [mailto:dotnet-owner@xxxxxxxxxxx] On
: Behalf Of Phil Best
: Sent: Friday, 3 December 2004 10:52 AM
: To: Stanski DotNet Group
: Subject: [aus-dotnet] Microsoft.Jet.OLEDB.4.0
:
: Hi,
: Has anybody had experience talking to Microsoft Access files?
:
: Please advise:
:  - Is this the correct connection string
: "Provider=Microsoft.Jet.OLEDB.4.0,
: Data Source= ......"
:  - What breed of SQL does it use?
:
: regards, Phil.
:
: Phil Best BSc(CompSc) AscDipElecEng

_________________
You are a part of the Australian "dotnet" mailing list.
To unsubscribe send "unsubscribe dotnet" or to re-subscribe send "subscribe
dotnet Your Name" in the body of the email to: imailsrv@xxxxxxxxxxx
List managed by: http://www.stanski.com



_________________
You are a part of the Australian "dotnet" mailing list.
To unsubscribe send "unsubscribe dotnet" or to re-subscribe send "subscribe dotnet Your Name" in the body of the email to: imailsrv@xxxxxxxxxxx
List managed by: http://www.stanski.com