Lately I've been doing a lot of importing and exporting of data to text files using stored specs. To see what fields and sizes a spec contatins I have been going to the File menu of Tables, click on Get External Data/Import. When the Open menu comes up, I click on any random text file. Then when the Import dialog starts I can get to the spec by clicking the Advanced button. I can then copy it to spreadsheet for documentation. Is there an easier or automated way to document Import/Export specs in ACCESS 2003?
I am trying to complete a macro that starts with importing of a text file. However, when I go to complete the steps in the macro, I do not see the specs for the import file that i created. There is a dropdown with a few specs for me to choose from in the box titled "Specification Name" when I am completing the action titled ImportExport Text. However, none of those specs are the right ones.
When I go to "Saved Imports" I can plainly see the import that I am interested in. So is a Saved Import different than a spec? If so, what steps do I need to do to create the spec?
Some time ago I did up an Access database for a friend. He told 2 friends and they told 2 friends and now several people would like a demo version of the database with documentation.
I usually don't give much thought to documentation as my databases tend to be stand alone to perform a specific set of functions.
Could someone point me in the right direction for the "generally accepted" method of Microsoft Access documentation. A template or somthing like that would be most helpful.
Hi All! I have created access Application and would like to document it. Do u guys have any samples, or maybe you have documented some aplication before...
Hello. Does anyone happen to know if the Specs... created in one database, can be copied over to another? I set up a particular database with file import specs for hundreds of fields, but I've outgrown the database file size and I need to create a new database with the same specs.
I have two tables that need to be exported on one .txt file.
One table has the header record. And the 2nd table has the detail record.
My issue is as follows: 1. Need to create one .txt file 2. The header record has one set of export specs and the detail record has a different set of export specs. 3. The first line is the header record, and 2nd line is the detail record.
Example below: H Abraham Armenta January Cake 00123 D Father Saturday 02536 00123
Both tables have a common control number - in this case represented by the 00123. I just cannot figure out how to accomplish this..
I have the following piece of code for importing the .csv files from a selected folder and then renaming them into 'imported & filename' if succesful and 'failed & filename' if import failes for whatever reason (bad formating, etc.).
The problem is that the first time it encounters a 'bad' file after another, instead of going again to the Error handler, the command
gives me the default MS Access error, namely 2391. I would like it to go the the Error_handler again ang follow the course of actions and rename the files into 'failed' and 'imported'.
Here's the code:
Sub ImportActivitate() Dim strFile As String 'Filename's Dim strFileList() As String ' File Array Dim intFile As Integer 'Number of files Dim filename As String, sFullName As String, sFilename As String DoCmd.SetWarnings False
[code]....
Also, how can I make the routine stop cycling through the files after I renamed them all?
I want to make a database of diseases (need to learn them for school and would like a serchable database on my smart phone for future reference). Unfortunately spent a lot of time making hundreds of pages of word tables before i realized a database would be better. See attached image or pdf. Is there a way to import the tables to Access?
I need to preserve the hierarchic info in the nested bullet point lists. E.g. under treatment i might have a point called Acute treatment, with sub-levels, Step 1, Step 2, etc. with their own sub-levels. I need to maintain this relational hierarchic info.
At the moment i am trying to produce a button which my users can click on to import some data from Excell to Access.
When i just go through it manually, ie file> import etc, the table fom Excel appears in access perfectly, but when i try using my button it brings up the following message:
Field 'F1' doesn't exist in the destination table 'Sheet2'.
The button runs off a macro. This is what i have for each option:
Action:TransferSpreadsheet
Transfer type: Import Spreadsheet type:Microsoft Excel 3 Table name:Sheet2 File name:the file location Has filed names:No Range:
I would be grateful if anyone could help and let me know where i am going wrong.
if you import using external file/import access just constructs tables of each individual xml tag, populated with the various values, not linked in any way
how do you get an invoice table, and invoice line table, etc, populated with appropriate data.
I guess this will be my last plea for help as to why an xml file will import the data into access 2003 (on my home PC) but not import the data, only the fields, on my work PC.
In both importings I'm indicating to indicate data and structure. Could it be the difference between versions? Perhaps a restriction at the end of my work environment?
I am not sure if this topic has been coverd in access-programmers forum but I'll ask any way.
I have thousands of records stored in excel (1NF). I have a access db to improve the need to have so many records duplicated.
Is their a way, via an action query (if so what one - update, append, cross tab etc) or another method to import the records and put them into related table.
For example, the current 1NF record columns are as follows >
Of course as organisation is the parent table, their is no problem doing a simple cut and paste, but i can work out how to put related records in a related table. Can you help?
Not sure where to post this question, so I put it in the general section,
I have an old db that i would like to import into a new be db of a newer version i wrote of this db. Is there any way something like an append query will add the records from one database to another?
or do i have to import then append then delete?
I have read several posts on this forum reference importing but all of them are from excel spreadsheets. Can this even be done??
I have been asked to recreate an existing database which was done in FileMaker into Access. Rather than re-enter all the data which is in there, can I just import it into Access? I tried exporting the FileMaker data into Lotus 123 format and then inporting it to Access that way. Filemaker has a bad habit of not exporting duplicate entries. I need this data as well. Any suggestions would be greatly appreciated.
I have got a Microsoft Access Database table with a few hundered records, I have got a excel or csv file with the same table but its got changes, deleted records and new records added.
What I want to do is replace the info in the access table with the new data that I want to import in. But I don't want duplicates and I want it to add, delete, modify records.
I know in MySQL you can use a Replace Query that does what I want. But the database I am working on is Microsoft Access.
Is their a solution in MS Access that I can tell it to point to a Excel Spreadsheet, or csv file and replace existing records with the changes, delete and add.
Hi. I have a db, where the main table is linked via an ODBC connection to a SQL server db. Want I would like to do is, either by code or a macro, import the information from the ODBC link , rather than "File", "Get External Data" etc etc. This way, the code or macro would run everytime the db is closed, and the information is stored in the db as a table..... just as a backup
I have tried the various "Transfer Database" with macros, but nothing seems to work
I don't know whether this would have any bearing on the answer but I do not have write permisisons on the SQL server, and it does not have a primary key.......as far as I am aware.
I need to import a form to an access 2007 database (from another access 2007 database) but on the External Data menu group, under the Import section, the Access option is greyed out (all other options are available).
I performed this same function yesterday and the Access option wasn't greyed out.
I've also opened up yesterday's backup of the DB and the Access option is greyed out in that too...
I am having to import data from a txt file on a daily basis. The date format in one of the fields is:30-Sep-2004 09:40:57 PM EDT. I want this to be in a short date format. I don't care about the time at all. If I try to import the data with this field set to Date/Time (regardless of format) it simply deletes the data in that field and goes to the next. If I import it as a Text field, it brings the date in as above.
Once the data is imported to the table, I can change the property of the field to Date/Time --> Short Date and it does the conversion. Is there a way to do this conversion automagically? I can't quite get any of the queries to work.
I'm trying to import some data from an excel sheet to a table in my database. The import wizard won't allow me to import the data into an existing table, only into a new one which is a nuisance. The data formats are the same. Any idea's what might me wrong Please.
I have lots of CSV files that are per day and are as follows:
File 1:
Username Time Bob 2 Joe 6
File 2: Username Time Joe 8 Sue 6
Essentially what I want to do is import each file into one table where if the username is not in the database it creates it, if its already in there a new column is created with the date. I dont mind creating multiple tables for each date and merging them.
So after those two files above were imported my table would look like this:
Username Time1 Time2 Bob 2 0 Joe 6 8 Sue 0 6
There are not many individual dates for that to be a problem, but there are over 5k different usernames in each file so I can't eyeball anything lol.
I am fairly new to access, but I am seasoned in MYSQL and Oracle. I've done some light searching on these forums and have not really come accross anything I need.