| Thread | Last Post | Replies |
|
| validating excel -> access imports | 15 Jan 2004 03:22 GMT | 1 |
From time to time, we receive datasets from an external organization in excel format. We want to run a series of validations and conversions on this data before we save it as a "trusted" data table.
|
| Importing/Exporting XML in Access 2000 | 15 Jan 2004 03:17 GMT | 1 |
Does anyone know how to import XML files into Access 2000, as I can't find anyway that this is possible... Cheers.
|
| ODBC Password - SQL Server | 15 Jan 2004 01:17 GMT | 1 |
When I set up an ODBC Connection with SQL Server,how can I get the password to be saved so that the user isn't prompted every time they open the linked SQL table?
|
| Too Many Fields Defined | 15 Jan 2004 01:11 GMT | 2 |
I have been exporting a query to Excel spreadsheet just fine. I have now added 4 additional columns. Total columns is now 14 with the same rows at 820. I now get the error "Too Many Fields Defined". I can no longer
|
| Linked Table Manager does not display linked tables | 14 Jan 2004 22:03 GMT | 2 |
We have just installed Microsoft Office 2003 on top of Office 2002. I pulled up an Access routine and went to relink my linked tables to another set of the same tables on another server. However, when I called up the linked
|
| exporting Access 2002 queries as XML? | 14 Jan 2004 20:27 GMT | 2 |
Looking at the automation objects exposed by the Microsoft Access 10.0 Object Library, I see that the ExportXML method is accessible at the Application object level. From this, I assume that I can only export the
|
| "The Decimal field's precision is too small to accept the numeric you attempted to add" | 14 Jan 2004 18:05 GMT | 1 |
I'm using Access 2000 linking FoxPro Tables via ODBC When I link tables with numeric fields Access gives me an error: "The Decimal field's precision is too small to accept the numeric you attempted to add."
|
| Output via a macro | 14 Jan 2004 17:57 GMT | 4 |
I am getting the message when trying to run a macro created on another machine. "The format in which you are attempting to output the current object in not available."
|
| Exporting Relationships | 14 Jan 2004 17:34 GMT | 2 |
I have a database set up with a master copy, a front end and a back end. The master copy contains all of the info, and is then exported to the front and back ends periodically.
|
| Linking to multiple Excel tables | 14 Jan 2004 11:35 GMT | 2 |
I have a number of spreadsheets on a shared drive, all with the same columns in the same format, but information relating to different offices. I have linked them all individually into my database to
|
| Excel Still running | 14 Jan 2004 04:18 GMT | 2 |
Hi I have an SQL database that I ame retrieving records from, witrh an access ADP front-end. I am trying to write recordset results to an excel spreadsheet. I need to to
|
| Importing txt file | 14 Jan 2004 03:45 GMT | 3 |
I have an existing table that was setup for importing txt files to it. I recently tried to import a txt file to it and now I am getting an error. A "Type Conversion Failure on my Date/Time field. The data in the import wizard shows as a date/time field and the field in the ...
|
| Exporting phone number input masks to text | 14 Jan 2004 01:15 GMT | 2 |
Table has fields for both phone numbers and fax numbers. They both use the Phone Number input mask. When exporting to text, it is exported as a string of ten digits. nnnnnnnnnn
|
| Microsoft Access was unable to export the data | 14 Jan 2004 01:02 GMT | 1 |
When attempting to export data in a query and specifing XML I get the following error message: Microsoft Access was unable to export the data.
|
| Importing Date from CSV File | 14 Jan 2004 01:02 GMT | 1 |
I am linking a CSV file (comma delimited text) with a date field in "mmddyy" format. What's the easiest way to convert that to an ACCESS date format? Thanks in advance.
|