I've searched for quite some time to find all the information you have put together so neatly in this clip. Thank you so much and I'm looking forward to watching more from you.
Hi Phil, brilliant start to the video series! It came across really well, congratulations on that. Easy to follow, I look forward to seeing the next video. Thanks for doing it!
Thanks, I've found what I needed :) - I've never noticed how we can save and then use the importation options via VBA - this will save me hours and hours. If there will be special cases to manage, this is a very useful help to start. Very good video.
This is a great video. I have already been down this path, but still found this to contain a couple of new gold nuggets. One thing you did not dive into, and I think it may be important to some, is WHERE the import specification is being stored. Hint, it is in the hidden system objects (Navigation Options | Display Options). I'm unclear about this, but it has seemed to me that, when moving from one development computer to another, these specifications did not follow me. I could be wrong about that, but in case there is an issue of this type, the import specs are stored in a hidden system table. Thanks for the great tutorials!
Thank you for this video. The portion about the Import/Export specification solved a problem I've been having with a linked table. I've done a few Google searches and that seems to be a widely unknown ability.
Hi, Thanks a lot for the tutorial it's really helped me in my project, but I've got one issue in the source file there are two date/time fields first one formated as dd/mm/yy and the s3cound one formed as yyyy/mm/yy hh:nn:ss how can I apply this in my specification?
Unfortunately, this is not supported by import specs. As a workaround, do not import the text file directly but only link it with a spec treating the date columns as text. Then create an append query base on the linked CSV file in Access and convert each of the date columns using a custom VBA function.
Hi Phil, just wanted to know how we can import multiple csv files with varying numbers of columns, also I need only few mandatory columns to be inserted in to the access database which is fixed, can you please help me on this?
You would need to create different import specifications for each type of file then. In the spec you can define which columns you want to import and which to ignore.
You are very attentive. -- I accidentally imported the "CustomerNumber" field from the file into the ID field of the table once. That set the internal ID counter to the imported 7 digit number. This mistake is not included in the video. I later compacted the database. That reset the counter to the current max number from the table.
You can only handle this if the values in the csv are enclosed in delimiters, e.g. quotes. Otherwise you need to use another separator instead of the comma, e.g. pipe or semicolon.
I've searched for quite some time to find all the information you have put together so neatly in this clip. Thank you so much and I'm looking forward to watching more from you.
Your class saved me from a big problem. A strong direct embrace of Brazil.
Hi Phil, brilliant start to the video series! It came across really well, congratulations on that. Easy to follow, I look forward to seeing the next video. Thanks for doing it!
Thanks, I've found what I needed :) - I've never noticed how we can save and then use the importation options via VBA - this will save me hours and hours. If there will be special cases to manage, this is a very useful help to start. Very good video.
Thank you so much for such great presentation!
This is a great video. I have already been down this path, but still found this to contain a couple of new gold nuggets. One thing you did not dive into, and I think it may be important to some, is WHERE the import specification is being stored. Hint, it is in the hidden system objects (Navigation Options | Display Options). I'm unclear about this, but it has seemed to me that, when moving from one development computer to another, these specifications did not follow me. I could be wrong about that, but in case there is an issue of this type, the import specs are stored in a hidden system table. Thanks for the great tutorials!
You made my day, my import always failed....and you showed me why, this tricky decimal symbole, fooled me over and over again...thanks a lot
Really nice. Easy to follow and understand. Well structured. Great pace. Thanks!!!
Excellent video! Thanks for putting it together, Phil!
Thank you for this video. The portion about the Import/Export specification solved a problem I've been having with a linked table. I've done a few Google searches and that seems to be a widely unknown ability.
from Japan, Your express is very simple and clear. thanks!
thank you, I got it to work and now do an automated import for my reports!
Thanks again Phillip very valuable information.
Thanks Phil, Very easy to follow and very helpful.
Thanks this helped me out immensely.
Oh that's great tutorial, thank you very much for your effort.
Thanks you save my day
that was awesome!
Hi,
Thanks a lot for the tutorial it's really helped me in my project, but I've got one issue in the source file there are two date/time fields first one formated as dd/mm/yy and the s3cound one formed as yyyy/mm/yy hh:nn:ss how can I apply this in my specification?
Unfortunately, this is not supported by import specs.
As a workaround, do not import the text file directly but only link it with a spec treating the date columns as text.
Then create an append query base on the linked CSV file in Access and convert each of the date columns using a custom VBA function.
its very useful, thanks
Hi Phil, just wanted to know how we can import multiple csv files with varying numbers of columns, also I need only few mandatory columns to be inserted in to the access database which is fixed, can you please help me on this?
You would need to create different import specifications for each type of file then. In the spec you can define which columns you want to import and which to ignore.
Hi philip thanks for the replay,
One more query how we can ignore some columns . By using skip blanks method in the access specification?
Why, when you ran the import spec via VBA the first time did it produce huge ID numbers?
You are very attentive. -- I accidentally imported the "CustomerNumber" field from the file into the ID field of the table once. That set the internal ID counter to the imported 7 digit number. This mistake is not included in the video.
I later compacted the database. That reset the counter to the current max number from the table.
What if I have numbers with comma in my csv file import ?
You can only handle this if the values in the csv are enclosed in delimiters, e.g. quotes.
Otherwise you need to use another separator instead of the comma, e.g. pipe or semicolon.