Sql - SELECT INTO Statement Not Working, But Works When Ran Directly In Access

I am converting old VB6 code to VB.NET with ADO.NET (OleDB). This is my query that will create a blank table when ran in VB.NET, but then works when ran directly in Access. This code presumably also works in VB6, as I am using the same SQL:

SELECT qryAsOf.name, qryAsOf.type, 0 as opt, 0 as swap
INTO qryCon
FROM qryAsOf
LEFT JOIN qryLinked on qryAsOf.c = qryLinked.lc

I feel like this has something to do with the left join and select into being together, but like I said it is only VB that has an issue with it, Access handles it perfectly.Without the INTO line, this query returns all 600+ rows.

This DOES NOT WORK:

cm.CommandText = "CREATE TABLE qryCon (etc...)"
cm.ExecuteNonQuery()
cm.CommandText = "INSERT INTO qryCon SELECT ..." '(rest of query above without INTO line)
cm.ExecuteNonQuery

This DOES WORK:

cm.CommandText = "CREATE PROC qryCon AS SELECT ..." '(same select as above without INTO, again)
cm.ExecuteNonQuery

The CREATE PROC that does work is fine, except I need to insert data into it later, so I get errors about how I need an updatable table. I really want the end qryCon to be a table, but I can't seem to get that to work :(

*However, when I do something like this (using the stored proc (renamed) above which, if viewed in Access, is full of data)

cm.CommandText = "SELECT * FROM storedProc"
dr = cm.ExecuteReader

[code]....

This DOES NOT WORK! By the way, I removed the concatenation in the query for readability. It is correct in the actual project.