DataBase - SQL Server SQL to Access 2003
Asked By Geossl
08-Oct-09 10:19 PM
The following query is for SQL Server. How to convert this to Access 2003 SQL?
SELECT Organization.Name, Organization.Id AS OrganizationID,
Item.Id as Itemid, Item.CTitle, Item.Title,
AcceptList.*
FROM Organization
CROSS JOIN Item
LEFT JOIN (
SELECT S.OrganizationID, en.ItemID
FROM Event S, Program en
WHERE en.EventID = s.Id
AND en.Accepted = 1
GROUP BY S.OrganizationID, en.ItemID
) AcceptList ON AcceptList.OrganizationID = Organization.Id
and AcceptList.ItemID = Item.Id
where AcceptList.ItemID is null
SQL Server
(1)
AcceptList.OrganizationID
(1)
AcceptList.ItemID
(1)
Access 2003
(1)
Item.CTitle
(1)
Item.Title
(1)
AcceptList
(1)
Itemid
(1)
Stefan Hoffmann replied...
hi,
The cross join is the simple: .. FROM Organization, Item...
mfG
--> stefan <--
Geossl replied...
But the whole thing does not work...
Stefan Hoffmann replied...
hi,
Sorry, I thought it was obvious that you need another sub select, e.g.
SELECT *
FROM
(
SELECT T1.Id AS T1ID,
T2.ID AS T2ID
FROM Table1 T1, Table2 T2
) Q
LEFT JOIN (
SELECT *
FROM Table3 T3
) AL ON AL.ID = Q.T1Id AND AL.ID = Q.T2Id
mfG
--> stefan <--
Geossl replied...

Roger Jennings on Access / Sharepoint DataBase http: / / www.quepublishing.com / articles / article.aspx?p = 1606238 I was very dismayed this article, is it makes it pretty clear that in-house hosting of your Sharepoint server with Access Services to support browser-based Access apps is something only large companies will be able to afford, because the pricing and licensing for the Enterprise version is very, very steep. The alternative is hosted Sharepoint / Access Services, and the costs do not seem terribly high. It seems to me that the pricing is upside-down. Big enterprises do not want to deploy Access apps in the browser - - they will build their own .NET apps, browser-based or not 2010 does not really save them money (because of the 64-bit requirements of Sharepoint Server 2010, it could vastly increase those costs for organizations with legacy hardware). The features of Access 2010 used in conjunction with Sharepoint 2010 seem to me to be most compelling for
Might be outgrowing Access but daunted by SQL Server DataBase I am close to completing the consolidation of various small Access databases and a couple of Excel spreadsheets that my little company uses (5 staff) into an all encompasing Access database and I was planning on splitting the database when I was finished to allow more and more obvious to me that I am going to need to give staff access to this new database from remote locations (outside of our office network). Two staff members spent the last 10 hours downloading, installing and trying to get my head around Microsoft SQL Server 2008 Express and how it might help me out. It all started when I came
SQL Server DataBase Hall?schen, ich habe mit einem SQL Server noch nie was am Hut gehabt. Alles was ich bisher gemacht hatte, da war Access immer ausreichend. Nun aber ist eine Anforderung, das ein Backend auf einem SQL-Server laufen soll, wobei dar?ber noch nicht fertig diskutiert ist. Ich habe da noch eine alte Vollversion von VB6, dort ist ein SQL-Server dabei (fracht mich aber nicht welche Version, der Karton mit der VB6 steht noch
Access 2010 with Sharepoint 2010 DataBase I found this article http: / / sharepointproconnections.com / Articles / tabid / 149 to me was these two points: client." Hopefully this means you can test out the Access 2010 in a browser capabilities. 2.0 AA compliance. Level 1 browsers, which support 100 on other platforms. Level 2 browsers will have some limitations in rendering and behavior." Bob Access Discussions SQL Server (1) MySQL (1) Visual Basic for Applications (1) SharePoint (1) Access 2007 (1) Access 2010 (1) Office 2003 (1) Windows 7 (1) Well, the question is do you really need to go to
SQL query slow DataBase Hi In the code below I found that it takes 1.3 seconds to load. There is a possible reason, it reads from a local MDB file (access), and it reads from some 270000 rows (result some 15-20 rows, where the highest are counted 150000, 50000, 40000, 26000, remaining are 100's). This is probably more Access that Visual Studio, though - is there a way to split it up or cancel the query? And can I read this faster? string sql = EquipmentID(Equipment) + StartDate.ToOADate().ToString(FloatFormat, myCulture) + EndDate.ToOADate().ToString(FloatFormat, myCulture); sql + = " group by event_id, name"; _Log("Calc thread #2"); OleDbCommand com = new OleDbCommand(sql, con); _Log("Calc thread #3"); From #2 to #3 it takes 1.3 seconds. Remaing code takes less that 0.1 second. So the query is what slows it down. Access Discussions SQL Server (1) Linson Unlike Albert D. Kallal (1) MySQL (1) Windows Server 2003 (1) Visual