kolait,
the argument you've highlighted in your image refers to a RANGE object, and that doesn't actually mean a TABLE on a sheet, but rather it's one of the following options:
1) NAMED RANGE
2) RANGE LITERAL (for example: "A1:F5")
I'm 99% sure I'm right about this, but I've never used a macro in this way so I"d have to test it to be sure.
Seem to remember dealing with a similar question not too long ago but can't find it. Although table names are listed with range names in name manager, they are treated different than ranges.
I cannot find a single example of ImportExportSpreadsheet referencing Excel table name. Agree with Adam, can't reference Excel table with this command.
kolait,
this is what i'm talking about....this uses a RANGE LITERAL, not a RANGE OBJECT.
how do you want it modified to do what you need?
so are you saying that you've solved your own problem now that you know what to do?Thank you dear friend
I was wrong.
I should have named the range from this path in the photo.
Now label any boundaries in any object and write in the macro, the entry and exit will be done
so are you saying that you've solved your own problem now that you know what to do?
if you want to use a macro to import the ranges, I'm guessing you *will* have to throw them to separate tables. however, there is a possibility that either of these two lines of specs in the "range" argument of the macro object would work to import multiple ranges:Now I want to know how to import multiple ranges of Excel into an Access table.
Do I need to create an access table for each range?
1) "A1:F5";B3:F9";A2:E3", etc... (seperated by ";" symbols"
2) "A1:F5",B3:F9",A2:E3", etc... (seperated by "," symbols"
this is addressed with what I just said. but if you end up importing ranges into different tables, then yes, a query would be needed to consolidate them all.And then, with a query, do I get them all in one table or is there another way?
if you want to use a macro to import the ranges, I'm guessing you *will* have to throw them to separate tables. however, there is a possibility that either of these two lines of specs in the "range" argument of the macro object would work to import multiple ranges:I will not test this for you, as I've done enough already. you can do it yourself. and you might not even need " " (double quotes) around the multiple arguments either. when you import one literal range, it doesn't require quotes.this is addressed with what I just said. but if you end up importing ranges into different tables, then yes, a query would be needed to consolidate them all.Code:1) "A1:F5";B3:F9";A2:E3", etc... (seperated by ";" symbols" 2) "A1:F5",B3:F9",A2:E3", etc... (seperated by "," symbols"
is not what I intended to say. if you got things to work, I doubt it was with this. the semicolon is used as a parsing indicator in more advanced languages like java, PHP, and .net stuff. probably C and C++ too. sorry about that! I hope you got it all worked out.1) "A1:F5";B3:F9";A2:E3", etc... (seperated by ";" symbols"
kolait,
if you come back to this thread, I should point out that this:is not what I intended to say. if you got things to work, I doubt it was with this. the semicolon is used as a parsing indicator in more advanced languages like java, PHP, and .net stuff. probably C and C++ too. sorry about that! I hope you got it all worked out.
ok, but you haven't told us if you *did* get it solved. did you?
so do you still want help with it? I or others can run some local tests on our end to see if some other patterns will work.Hi
No
I was unable to enter a few different ranges.
I tested all the characters but it didn't.
But the selection of a naming range was correct.
probably not. his problem is in access, not in excel. he's trying to tell access to import multiple named and un-named ranges in a macro argument.