Search results

Neither of these steps changed anything. Scheduling the job earlier just moved the error earlier. I then converted the macro step that runs the query to a RunCode of a VBA function and had error handling set to display the error description. But still nothing displayed except the window...

Using an alias worked. Thanks!

Using SQL Server 2000, I've created a linked server to an Access 2003 database. The linked server name is StatsDb and the table in it is Employees. It works fine for simple select queries of that table data, but not when I use an inner join to a field (User) in that table. The join code in...

We've been running an Access macro every night for over a year. It updates a linked Access table using OBDC linked tables. But several weeks ago the macro started quitting after several steps. It was usually after a certain step but some nights it was on a different steps. In the morning we...

It didn't work. The client had actually used dates for the headers in a customized format (mmm-yy). We made a workaround by inserting a dummy row 2 and filling the cells with "$0". Then the Import Wizard gives all the Access fields the proper names and data types. Thanks for your input -...

We get an Excel spreadsheet every month from a client. Most of the columns have names like "Sep-01", "May-05", etc. Those columns contain the dollar amount received during that month. The problem comes when we import the data into an Access 2003 table. The Import Spreadsheet Wizard only...

I'm using Access 2003 and SQL Server 2000 Enterprise (recently upgraded from the non-Enterprise version). When I try to use DTS to import data from an Access database on a server drive, I get the following message in the DTS wizard: "OLE DB provider 'Microsoft.Jet.OLEDB.4.0' reported an error...

I'm using Access 2003 and SQL Server 2000 Enterprise (recently upgraded from the non-Enterprise version). When I try to use DTS to import data from an Access database on a server drive, I get the following message in the DTS wizard: "OLE DB provider 'Microsoft.Jet.OLEDB.4.0' reported an error...

All the tests used code to just start Access (no mention of a database or macro). I keep getting a "file not found" error even tho it is the correct path on the server drive. I removed the double quotes & got the same error. I also tried the following code (same results): Exec...

I'm trying to create a nightly job that will run a macro in an Access database. The database is called Stats.mdb and the macro is called mcrDaily. The single job step has a type of "Operating System Command" and has the following code: "C:\Program Files\Microsoft Office\Office11\MsAccess.exe"...

Thanks. Thanks, that syntax worked with the OutputTo method.

I'm trying to automate the creation of report snapshot whose name will vary each day. The snapshot name is in a textbox on a form. I have a macro that opens this form (hidden) and then uses OutputTo to make the snapshot. I tried the OutputTo action and got a file whose name was the textbox...

I tried: FROM NPVData.npvdata.tblProposals (got invalid object) then FROM NPVData.npvdata.dbo.tblProposals (got error 7399) I can't import the table into SQL because it's a linked table in an Access utility loaded on several dozen PCs and used daily by people who have restricted network...

I need to use an Access table (on a network drive) in a T-SQL script in SQL Server 2000. I used the following code to create a linked server on our server: EXEC sp_addlinkedserver @server = 'NPVData', @srvproduct = 'OLE DB Provider for Jet', @provider = 'Microsoft.Jet.OLEDB.4.0'...

Within a T-SQL script in SQL Server 2000, is there a way to read records in an Access table? The Access database is on a network drive (O:\Npv\Npv.mdb) and the table is called tblProposals. I want to insert seelcted fields into an SQL table.

Every month I download an Excel spreadsheet from a vendor and import it into Access 2003. Even tho the first row has column names, a dozen fields have incorrect names and data types and I have to manually change them each time. The spreadsheet has columns representing the amount spent for...

We have a table in MS SQL Server 2000 that has over 185 million records. We archived 155 million of those records and now want to delete those records from the original table. When we ran the following script, we got a message about an unnamed problem: Delete From dbo.notes with...

I changed the CREATE VIEW script for MS SQL Server 2000 so the WHERE clause is WHERE Acct = " & [Forms]![frmMain].[cboAcct] & " and got an "Invalid column name" error message when I ran the script. How were the double quotes and ampersands supposed to fix the problem?

I have an Access project in which the main form is based on a view. The WHERE clause in the view needs to equate the value of a table field to the value of a combobox on the form. In the script that creates the view, I get a syntax error when the clause is: WHERE Acct =...

That did it! Another instance of a cranial blindspot. Thanks.