Search results for query: *

I have an old Access 97 database that i need to upgrade to 2003. I can get most of the tables and some queries, but the forms and modules are locked. Is there a back door to beign able to get read/write priviliges for this DB? I a good with access, just not the security part of it, i can get...

I have been doing that for when i want to import into SQL Server. In this case, i want to export from SQL Server and import into Access, so the current connection that will execute the SSQL statement will be for access. I believe I just need to change the [MS ACCESS;DATABASE=" & DatabaseFrom...

I am running an Export table function that reads an sql server connection then imports a table into access db connection. I have code that reads an access db and imports a table into another (different) access db. this is the code: sSQL = "SELECT " & Columns & " INTO " & sTable & " FROM " &...

If the current connection is an access connection, how would I connect to the SQL Server table to import into access? sSQL = "SELECT " & Columns & " INTO " & sTable & " FROM " & sTable & " IN '' [MS ACCESS;DATABASE=" & DatabaseFrom & ";TABLE=" & Table & "]" oConn.Execute sSQL

Here is what I currently have that errors out saying 'Syntax error in FROM clause' sSQL = "SELECT * INTO [BarcodeMasks] FROM OPENROWSET('MSDASQL','DRIVER={SQL Server}; SERVER=JEFF;DATABASE=PTSQL;UID=dbo;PWD=', [BarcodeMasks])"

The table does not exist in the current database, this is part of an 'export table' function. One question, how do I specify what database to use as part of the OPENROWSET function?

There is no WHERE clause...it should be doing the whole table. ARe you saying i should make the statment like this: SELECT * INTO [BarcodeMasks] FROM [BarcodeMasks] IN (Select * FROM OPENROWSET('MSDASQL','DRIVER={SQL Server};SERVER=JEFF;UID=dbo;PWD=',[BarcodeMasks]))

I am converting some sql statements that were designed for an Access database connection to make them work with SQL Server. Most of the time this has meant to use OPENROWSET for the external SQL Server connection while using a local Access table connection. Can anyone tell me why this...

what is wrong with this conversion? FROM- sSQL = "INSERT INTO Packages " & _ "SELECT * FROM [MS Access;DATABASE=" & DatabaseFrom & ";].Packages MSP WHERE " & _ " MSP.PackageID NOT IN (SELECT PackageID FROM Packages) AND MSP.PackageID NOT IN (SELECT PackageID FROM Deleted)" TO-...

This is already an already completed application, so changing it here would also constitute changing it in many other locations. I can just put brackets around it.

one is still an access database, and the other is SQL server. can i use "Deleted" as a table name?

I have to do a data transfer between two databases. The code was already written to move data between two access MDB files. I am changing the backend database to SQL Server, which inevitably will change the SQL statement. here is the statement for two MDB's - "INSERT INTO Packages " & _...

just as a reminder, how would i convert this string? sSQL = "INSERT INTO Packages " & _ "SELECT * FROM [MS Access;DATABASE=" & DatabaseFrom & ";].Packages MSP WHERE " & _ " MSP.PackageID NOT IN (SELECT PackageID FROM Packages) AND MSP.PackageID NOT IN (SELECT PackageID FROM...

It works...I had a UDL in the development directory and it was set to something else. i changed it and it ran. so what happens if the udl points to another server that isnt local?

yep

Its wierd, I did that, and it now says it can't find the file and I can see it on the C:\...wierd

it runs fine in query analyzer. here is the error desc: [OLE/DB provider returned message: 'C:\Program Files\IntelliTrack\Package Track\Transfer12212005115147.mdb' is not a valid path. Make sure that the path name is spelled correctly and that you are connected to the server on which the file...

Here is the ssql: ? ssql Update P SET TrackingNo = MSP.TrackingNo, RecipientID = MSP.RecipientID, PackageTypeID = MSP.PackageTypeID, LocationID = MSP.LocationID, CarrierID = MSP.CarrierID, MailRoomID = MSP.MailRoomID, ReceivedUserID = MSP.ReceivedUserID, ReceivedDate = MSP.ReceivedDate...

What should i test next? i am still getting errors..

i am opening the connection using a UDL (FILENAME="C:\...)