StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
9167999
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2012-02-06T22:04:36.677
FavoriteCount
0
LastActivityDate
2012-02-06T22:19:00.253
LastEditDate
2012-02-06T22:19:00.253
LastEditorUserId
1186165
OwnerUserId
1186165
ParentId
9103867
PostTypeId
2
Score
2
ViewCount
0
LastEditorDisplayName
text
Body
The problem is that you're using VBA code IN the SQL statement. The following line will compile but fail upon execution: <pre><code>Cn.Execute "INSERT INTO Project_Names IN 'D:\Tool_Database\Tool_Database.mdb' SELECT * FROM Worksheets("NewProj").Range("A2").Value" </code></pre> It fails because you're still in the SELECT statement when you make use the VBA functions of Worksheets(), .Range, and .Value. IIRC, you should be able to use SQL syntax to select a particular range from a sheet. The proper syntax for that should be: <pre><code>"SELECT * FROM [Sheet$]" </code></pre> If you want a particular range then you'd try: <pre><code>"SELECT * FROM [Sheet$A1:C20]" </code></pre> There's a Microsoft article on this at: <a href="http://support.microsoft.com/kb/257819" rel="nofollow">http://support.microsoft.com/kb/257819</a> if you're looking for more information on using ADO with Excel. The Scripting Guys also wrote a decent article that helped me understand it a few years back: <a href="http://technet.microsoft.com/en-us/library/ee692882.aspx" rel="nofollow">http://technet.microsoft.com/en-us/library/ee692882.aspx</a>. Hopefully that helps you solve your problem. However, I will leave you with one word of warning. I remember running into some really weird issues when querying an already open Excel spreadsheet when I was first using this code. If I was querying an Excel spreadsheet that was already open then I would run into an issue where memory would be leaked and Excel would eventually run out of memory to use. The only way to solve the problem was to close Excel entirely. It also didn't matter whether the ADO references were properly closed/cleared or not. In fact, I just Googled it to double check and here's an article on the bug: <a href="http://support.microsoft.com/default.aspx?scid=kb;en-us;319998&Product=xlw" rel="nofollow">http://support.microsoft.com/default.aspx?scid=kb;en-us;319998&Product=xlw</a>.
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POUsing INSERT INTO to write data into access database
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. USKittoes0124
UserOwnerUserId
1. USKittoes0124
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. POUsing INSERT INTO to write data into access database
 singulars
 PostTypePostTypeId
 PTQuestion
PostsParentIdCreationDate
1. This table or related slice is empty.
VotesPostIdCreationDate
1. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTAcceptedByOriginator
CommentsPostId
1. This table or related slice is empty.

Querying!

Guidance

A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.