<div>
You may have to use automation - in Access to open an Excel instance, open the workbook, and read the values of the range in question directly.
</div>


bfuchs

<div>
You can also predefine the field types and lengths in the Access table, and then, instead of simply linking the Excel file, you can use TransferSpreadsheet method to insert the values from Excel into Access. &nbsp;This gives you a bit more flexibility in the process.<br />
<br />
Dale
</div>


Topic Advisor

Mark Wills

<div>
Another solution might be to export the Excel sheet to a CSV file and then import it. I have had trouble in the past with Excel because sometimes there are hidden fields on the Spreadsheet which causes problems while linking. Once you create the CSV file you can examine it fro consistency.
</div>


<div>
Hi Experts,<br />
<br />
The following is the query used to import the data from that linked Excel (V_Visit_Note_Export) sheet into my Access table (Skilled_Nursing_Visit_Not<wbr />e).<br />
<br />
Can someone post the code will have to use instead, when using those methods above?<br />
<br />

<pre><code class="code-1 nolinks" id="code-20-42745681-1"><span>INSERT INTO Skilled_Nursing_Visit_Note ( SNV_ID, Client_Last_Name, Visit_Date, Date_Of_Birth, Medical_Record_Number, Shift_From_Hour, Shift_To_Hour, Purpose_Of_Visit_Goal, Temp, Pulse, RR, BP, O2_Saturation, O2_In_Use, Respiratory_Lung_Sounds, Respiratory_Breathing_Pattern, Bipap, Cpap, Vent, Vent_BIPAP_Settings, Cardiovascular_Skin_Color, Skin_Temp, Cardiovascular_Edema, Neuro_Alert, Neuro_Oriented, Neuro_Self_Directing, Neuro_Dev_Delay, Neuro_Deficits, Neuro_Notes, GI_Oral_Tube_Feeding, Current_Feeds, Gastric_Residuals_Present, Residual_Volume, MD_Called, Abdominal_Assessment, Feeding_Tolerance, GU_Incontinent, Number_Of_Diaper_Changes, Urine_Stool_Volume_Description, Bedbound, WheelChair, Ambulatory, Mobility_Aids, Contractures, Musculoskeletal_Notes, Pain_Score, Pain_Notes, Medication_Changes, Medication_Changes_2, Integument_Skin_Assessment, Skin_Care_Measures_Taken, Home_Environment_Safety, Treatments_Administered, Patient_Response, Instructions, Understanding, Plan_Goal, Nurse_Signature_Last_Name, Signature, Date_Signed, Nurse_Name_Stamp_SNV, Nurse_User_ID_num_SNV, Medication_Changes_Yes, Acknowledge_Accuracy, Trach, CCM_Informed, Tube_Type, Reviewed_Status, Reviewed_By, Reviewed_stamp, Client_First_Name, Nurse_Signature_First_Name, Shift_From_Minute, Shift_To_Minute, Patient_Unable_To_Sign, Reason, Status )</span>
<span>SELECT V_Visit_Note_Export.SNV_ID, V_Visit_Note_Export.Client_Last_Name, V_Visit_Note_Export.Visit_Date, V_Visit_Note_Export.Date_Of_Birth, V_Visit_Note_Export.Medical_Record_Number, V_Visit_Note_Export.Shift_From_Hour, V_Visit_Note_Export.Shift_To_Hour, V_Visit_Note_Export.Purpose_Of_Visit_Goal, V_Visit_Note_Export.Temp, V_Visit_Note_Export.Pulse, V_Visit_Note_Export.RR, V_Visit_Note_Export.BP, V_Visit_Note_Export.O2_Saturation, V_Visit_Note_Export.O2_In_Use, V_Visit_Note_Export.Respiratory_Lung_Sounds, V_Visit_Note_Export.Respiratory_Breathing_Pattern, V_Visit_Note_Export.Bipap, V_Visit_Note_Export.Cpap, V_Visit_Note_Export.Vent, V_Visit_Note_Export.Vent_BIPAP_Settings, V_Visit_Note_Export.Cardiovascular_Skin_Color, V_Visit_Note_Export.Skin_Temp, V_Visit_Note_Export.Cardiovascular_Edema, V_Visit_Note_Export.Neuro_Alert, V_Visit_Note_Export.Neuro_Oriented, V_Visit_Note_Export.Neuro_Self_Directing, V_Visit_Note_Export.Neuro_Dev_Delay, V_Visit_Note_Export.Neuro_Deficits, V_Visit_Note_Export.Neuro_Notes, V_Visit_Note_Export.GI_Oral_Tube_Feeding, V_Visit_Note_Export.Current_Feeds, V_Visit_Note_Export.Gastric_Residuals_Present, V_Visit_Note_Export.Residual_Volume, V_Visit_Note_Export.MD_Called, V_Visit_Note_Export.Abdominal_Assessment, V_Visit_Note_Export.Feeding_Tolerance, V_Visit_Note_Export.GU_Incontinent, V_Visit_Note_Export.Number_Of_Diaper_Changes, V_Visit_Note_Export.Urine_Stool_Volume_Description, V_Visit_Note_Export.Bedbound, V_Visit_Note_Export.WheelChair, V_Visit_Note_Export.Ambulatory, V_Visit_Note_Export.Mobility_Aids, V_Visit_Note_Export.Contractures, V_Visit_Note_Export.Musculoskeletal_Notes, V_Visit_Note_Export.Pain_Score, V_Visit_Note_Export.Pain_Notes, V_Visit_Note_Export.Medication_Changes, V_Visit_Note_Export.Medication_Changes_2, V_Visit_Note_Export.Integument_Skin_Assessment, V_Visit_Note_Export.Skin_Care_Measures_Taken, V_Visit_Note_Export.Home_Environment_Safety, V_Visit_Note_Export.Treatments_Administered, V_Visit_Note_Export.Patient_Response, V_Visit_Note_Export.Instructions, V_Visit_Note_Export.Understanding, V_Visit_Note_Export.Plan_Goal, V_Visit_Note_Export.Nurse_Signature_Last_Name, V_Visit_Note_Export.Signature, V_Visit_Note_Export.Date_Signed, V_Visit_Note_Export.Nurse_Name_Stamp_SNV, V_Visit_Note_Export.Nurse_User_ID_num_SNV, V_Visit_Note_Export.Medication_Changes_Yes, V_Visit_Note_Export.Acknowledge_Accuracy, V_Visit_Note_Export.Trach, V_Visit_Note_Export.CCM_Informed, V_Visit_Note_Export.Tube_Type, V_Visit_Note_Export.Reviewed_Status, V_Visit_Note_Export.Reviewed_By, V_Visit_Note_Export.Reviewed_stamp, V_Visit_Note_Export.Client_First_Name, V_Visit_Note_Export.Nurse_Signature_First_Name, V_Visit_Note_Export.Shift_From_Minute, V_Visit_Note_Export.Shift_To_Minute, V_Visit_Note_Export.Patient_Unable_To_Sign, V_Visit_Note_Export.Reason, V_Visit_Note_Export.Status</span>
<span>FROM Skilled_Nursing_Visit_Note RIGHT JOIN V_Visit_Note_Export ON Skilled_Nursing_Visit_Note.SNV_ID = V_Visit_Note_Export.SNV_ID</span>
<span>WHERE (((V_Visit_Note_Export.Status) Is Null Or (V_Visit_Note_Export.Status)&lt;&gt;&quot;draft&quot;) AND ((Skilled_Nursing_Visit_Note.SNV_ID) Is Null)) OR (((V_Visit_Note_Export.Status)=&quot;draft&quot;) AND ((Skilled_Nursing_Visit_Note.SNV_ID) Is Null) AND ((V_Visit_Note_Export.Deleted)=True));</span>
</code></pre>
<br />
Thanks,<br />
Ben
</div>


<div>
I realized that linking to CSV does not have that limitation, there I can specify the datatypes (see attached).<br />
<br />
Now I have an option of downloading these files in CSV format instead, however would need your help on how to modify the code below to accommodate this change...<br />
<br />

<pre><code class="code-10 nolinks" id="code-20-42745715-1"><span>    sExt = &quot;XLSX&quot;</span>
<span>    </span>
<span>    sDestinationFolder = &quot;C:\Application\&quot;</span>
<span>       sDownloadFolder = &quot;F:\Conversion\Caspio\&quot;</span>
<span>    sBackupFolder = &quot;E:\CaspioBackups\&quot;</span>
<span> </span>
<span>    </span>
<span>    sLastFile = &quot;CaspioTables.zip&quot;</span>
<span>    i = UnZip(sDownloadFolder &amp; sLastFile, sDestinationFolder, False)</span>
<span>    </span>
<span>    If i = 0 Then</span>
<span>        sDestinationFolder = &quot;C:\Application\&quot;</span>
<span>        </span>
<span>        If Dir(sDestinationFolder &amp; NewestFile(sDestinationFolder, &quot;*.&quot; &amp; sExt)) &lt;&gt; &quot;&quot; Then</span>
<span>            If Dir(sDestinationFolder &amp; &quot;Tables.&quot; &amp; sExt) &lt;&gt; &quot;&quot; Then</span>
<span>                Kill sDestinationFolder &amp; &quot;Tables.&quot; &amp; sExt</span>
<span>            End If</span>
<span>            Name sDestinationFolder &amp; NewestFile(sDestinationFolder, &quot;*.&quot; &amp; sExt) As sDestinationFolder &amp; &quot;Tables.&quot; &amp; sExt</span>
<span>        End If</span>
<span>    End If</span>
</code></pre>
<br />
Currently the Excel option downloads all sheets into one spreadsheets divided by sheets.<br />
<br />
However the CSV option will save two files into one zip file named &quot;C:\Users\bfuchs\Downloads<wbr />\Tables_20<wbr />18-Nov-29_<wbr />1738.zip&quot;<br />
<br />
So that means after unzipping those files I have to rename them (removing the date/time from the file names), see 2nd attachment.<br />
<br />
Actually this was the reason I didn't went with the CSV option to begin with...<br />
<br />
How can I accomplish that?<br />
<br />
Thanks,<br />
Ben<br />
<a href="https://filedb.experts-exchange.com/incoming/2018/11_w48/1405443/Untitled.png" target="_blank" class="file-inline" title="1 (41 KB)"><svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 512 512"><path d="M67.508 468.467c-58.005-58.013-58.016-151.92 0-209.943l225.011-225.04c44.643-44.645 117.279-44.645 161.92 0 44.743 44.749 44.753 117.186 0 161.944l-189.465 189.49c-31.41 31.413-82.518 31.412-113.926.001-31.479-31.482-31.49-82.453 0-113.944L311.51 110.491c4.687-4.687 12.286-4.687 16.972 0l16.967 16.971c4.685 4.686 4.685 12.283 0 16.969L184.983 304.917c-12.724 12.724-12.73 33.328 0 46.058 12.696 12.697 33.356 12.699 46.054-.001l189.465-189.489c25.987-25.989 25.994-68.06.001-94.056-25.931-25.934-68.119-25.932-94.049 0l-225.01 225.039c-39.249 39.252-39.258 102.795-.001 142.057 39.285 39.29 102.885 39.287 142.162-.028A739446.174 739446.174 0 0 1 439.497 238.49c4.686-4.687 12.282-4.684 16.969.004l16.967 16.971c4.685 4.686 4.689 12.279.004 16.965a755654.128 755654.128 0 0 0-195.881 195.996c-58.034 58.092-152.004 58.093-210.048.041z"/></svg>Untitled.png</a><br />
<a href="https://filedb.experts-exchange.com/incoming/2018/11_w48/1405445/Untitled.png" target="_blank" class="file-inline" title="2 (129 KB)"><svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 512 512"><path d="M67.508 468.467c-58.005-58.013-58.016-151.92 0-209.943l225.011-225.04c44.643-44.645 117.279-44.645 161.92 0 44.743 44.749 44.753 117.186 0 161.944l-189.465 189.49c-31.41 31.413-82.518 31.412-113.926.001-31.479-31.482-31.49-82.453 0-113.944L311.51 110.491c4.687-4.687 12.286-4.687 16.972 0l16.967 16.971c4.685 4.686 4.685 12.283 0 16.969L184.983 304.917c-12.724 12.724-12.73 33.328 0 46.058 12.696 12.697 33.356 12.699 46.054-.001l189.465-189.489c25.987-25.989 25.994-68.06.001-94.056-25.931-25.934-68.119-25.932-94.049 0l-225.01 225.039c-39.249 39.252-39.258 102.795-.001 142.057 39.285 39.29 102.885 39.287 142.162-.028A739446.174 739446.174 0 0 1 439.497 238.49c4.686-4.687 12.282-4.684 16.969.004l16.967 16.971c4.685 4.686 4.689 12.279.004 16.965a755654.128 755654.128 0 0 0-195.881 195.996c-58.034 58.092-152.004 58.093-210.048.041z"/></svg>Untitled.png</a>
</div>


Untitled.png

<div>
Ben,<br />
<br />
As much as I prefer using CSV files, I've found that many of these have commas embedded within quoted text strings, and Access does not handle these well (neither does SQL Server for that matter). &nbsp;You might want to take a look at the article I wrote on <a href="https://www.experts-exchange.com/articles/31012/Reading-a-wide-CSV-file-255-columns-using-Access-and-SQL-Server.html" rel="ugc">Reading Wide CSV Files</a>. &nbsp;This was specifically about reading CSV files with &gt;&nbsp;255 columns, but ended up being more about parsing CSV files and eliminating the embedded commas within text strings.
</div>


<div>
@Dale,<br />

<blockquote>
As much as I prefer using CSV files, I've found that many of these have commas embedded within quoted text strings, and Access does not handle these well
</blockquote>
In my scenario it looks like its handling fine all columns including commas (see attached).<br />
Therefore if I find a way to rename those files by code (as mentioned above) I would be happy...<br />
Thanks,<br />
Ben<br />
<a href="https://filedb.experts-exchange.com/incoming/2018/11_w48/1405449/Untitled.png" target="_blank" class="file-inline" title="1 (190 KB)"><svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 512 512"><path d="M67.508 468.467c-58.005-58.013-58.016-151.92 0-209.943l225.011-225.04c44.643-44.645 117.279-44.645 161.92 0 44.743 44.749 44.753 117.186 0 161.944l-189.465 189.49c-31.41 31.413-82.518 31.412-113.926.001-31.479-31.482-31.49-82.453 0-113.944L311.51 110.491c4.687-4.687 12.286-4.687 16.972 0l16.967 16.971c4.685 4.686 4.685 12.283 0 16.969L184.983 304.917c-12.724 12.724-12.73 33.328 0 46.058 12.696 12.697 33.356 12.699 46.054-.001l189.465-189.489c25.987-25.989 25.994-68.06.001-94.056-25.931-25.934-68.119-25.932-94.049 0l-225.01 225.039c-39.249 39.252-39.258 102.795-.001 142.057 39.285 39.29 102.885 39.287 142.162-.028A739446.174 739446.174 0 0 1 439.497 238.49c4.686-4.687 12.282-4.684 16.969.004l16.967 16.971c4.685 4.686 4.689 12.279.004 16.965a755654.128 755654.128 0 0 0-195.881 195.996c-58.034 58.092-152.004 58.093-210.048.041z"/></svg>Untitled.png</a>
</div>


<div>
As Dale suggested, simply import the spreadsheet.<br />
<br />
If you go to External Data, New Datasource, From File, Excel, and go through the Wizard, you can specify the column data types<br />
<br />
They have to be accurate because Access will complain about &quot;row being too long / large&quot; <br />
<br />
You can specify table name to create for the import - make it something unique like &nbsp;&quot;V_Visit_Note_Export_Stagi<wbr />ng&quot;<br />
<br />
If need be, you can go back (after the event) and further refine the column sizes in Design View of the Table.<br />
<br />
But that is just getting it into Access.<br />
<br />
You still have data types to comply with in getting the INSERT resolved (go from Access to SQL Server)<br />
<br />
There is no silver bullet, just elbow grease, some hair pulling, frustration and ultimately success.<br />
<br />
Can we now go back to your other thread and finish off that work ?
</div>


<div>
Hi Mark,<br />

<blockquote>
If you go to External Data, New Datasource, From File, Excel, and go through the Wizard, you can specify the column data types
</blockquote>
Actually depends how you want do it, if you use the wizard to import, then yes you get that option to select datatype etc...<br />
However unfortunate I cannot do that within my Access app, as this will blow up my entire app, <br />
<br />
I need a way to link it and perform the insert operation from one external data source to the other (currently from Excel/CSV to Access, and eventually from Excel/CSV to SQL Server).<br />
<br />

<blockquote>
Can we now go back to your other thread and finish off that work ?
</blockquote>
As mentioned in the other thread, I cannot resume that until this gets resolved, especially that we're not sure yet which file type we are going to end up using, and it maight very well be that by working with CSV, we are going to face different issues (happen to be I tested that earlier today, CSV-&gt;SQL and got different error message...).<br />
<br />
Don't worry, we are going get to that too, sooner or later-:)<br />
<br />
Thanks,<br />
Ben
</div>


<div>
@Ben,<br />
<br />
That query you posted above is inserting into Skilled_Nursing_Visit_Note<wbr /> from V_Visit_Note_Export<br />
<br />
How can that be when you cannot import your Spreadsheet into V_Visit_Note_Export ?<br />
<br />
You need to worry about the definition of the table / data you are importing from / to to make sure there is no truncation. <br />
<br />
Which columns are being truncated ?<br />
<br />
Or, is this yet another different approach to try to work around the problems of using Access to update/insert a SQL Server Table ? Hence posting that particular query ?
</div>


<div>
Hi,<br />

<blockquote>
That query you posted above is inserting into Skilled_Nursing_Visit_Note<wbr /> from V_Visit_Note_Export
</blockquote>
Right.<br />

<blockquote>
How can that be when you cannot import your Spreadsheet into V_Visit_Note_Export ?
</blockquote>
Where do you see that?<br />
V_Visit_Note_Export is the name of my Access linked table which is linked to a spreadsheet.<br />
Currently the insert query works but fields are getting truncated.<br />
See attached how are fields defined after I finish linking, all text are short text regardless of how much data they indeed contain in Excel.<br />
Perhaps this is an Access bug...<br />
Thanks,<br />
Ben<br />
<a href="https://filedb.experts-exchange.com/incoming/2018/12_w49/1405821/Untitled.png" target="_blank" class="file-inline" title="1 (93 KB)"><svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 512 512"><path d="M67.508 468.467c-58.005-58.013-58.016-151.92 0-209.943l225.011-225.04c44.643-44.645 117.279-44.645 161.92 0 44.743 44.749 44.753 117.186 0 161.944l-189.465 189.49c-31.41 31.413-82.518 31.412-113.926.001-31.479-31.482-31.49-82.453 0-113.944L311.51 110.491c4.687-4.687 12.286-4.687 16.972 0l16.967 16.971c4.685 4.686 4.685 12.283 0 16.969L184.983 304.917c-12.724 12.724-12.73 33.328 0 46.058 12.696 12.697 33.356 12.699 46.054-.001l189.465-189.489c25.987-25.989 25.994-68.06.001-94.056-25.931-25.934-68.119-25.932-94.049 0l-225.01 225.039c-39.249 39.252-39.258 102.795-.001 142.057 39.285 39.29 102.885 39.287 142.162-.028A739446.174 739446.174 0 0 1 439.497 238.49c4.686-4.687 12.282-4.684 16.969.004l16.967 16.971c4.685 4.686 4.689 12.279.004 16.965a755654.128 755654.128 0 0 0-195.881 195.996c-58.034 58.092-152.004 58.093-210.048.041z"/></svg>Untitled.png</a>
</div>


<div>
have you tried defining the fields in a staging table, and defining some of the fields (the long ones) as memo, and then, instead of linking to the spreadsheet, you import it into the staging table?<br />
<br />
I believe I recommended this in one of my previous posts.
</div>


<div>
Hi,<br />

<blockquote>
instead of linking to the spreadsheet, you import it into the staging table?
</blockquote>
Well for that will have to write code that reads a spreadsheet and perform this task, while currently I just have a link table and only running some queries to transfer from one source to the other...<br />
I believe linking to CSV can solve this issue, just a matter of mapping to the right datatype, currently working in that direction, will keep you posted.<br />
<br />
btw, I got a way to rename those CSV files (<a href="https://www.experts-exchange.com/questions/29127862/Remove-timestamp-from-file-name.html?anchor=a42746536&notificationFollowed=219124928&anchorAnswerId=42746536#a42746536" rel="ugc">https://www.experts-exchange.com/questions/29127862/Remove-timestamp-from-file-name.html?anchor=a42746536&notificationFollowed=219124928&anchorAnswerId=42746536#a42746536</a>), therefore I believe is just a matter of time till I get this up and running...<br />
<br />
Thanks,<br />
Ben
</div>


<div>
I honestly thought you were importing.....<br />
<br />
Yes, Excel as a Linked Table will only show the first 255 characters. That is a known limitation of linking directly to Excel.<br />
<br />
See : <a href="https://support.office.com/en-us/article/import-or-link-to-data-in-an-excel-workbook-a1952878-7c58-47b1-893d-e084913cc958#__link_to_data" rel="ugc">https://support.office.com/en-us/article/import-or-link-to-data-in-an-excel-workbook-a1952878-7c58-47b1-893d-e084913cc958#__link_to_data</a>&nbsp; and scroll down to the grey chart and look for truncated values.<br />
<br />
Also in that same article, there is a section on using the Wizard to import data and it clearly states (step 4) :
<blockquote>
Access reviews the first eight rows in each column to suggest the data type for the corresponding field. If the column in the worksheet contains different types of values, such as text and numbers, in the first eight rows of a column, the wizard suggests a data type that is compatible with all the values in the column — most often, the text data type.
</blockquote>
<br />
Which is why I posted above suggesting you use the Wizard and override the data types. However, I think you really need MEMO as Dale says above. There can still be issues with longtext.<br />
<br />
Not sure where or when I had the thought that you were importing the data, but clearly had that impression....
</div>


<div>
Hi,<br />

<blockquote>
Yes, Excel as a Linked Table will only show the first 255 characters.
</blockquote>
If only they would prompt us with a message (while starting the wizard of linking) informing that...why should someone think of this...(some software vendors put this kind of limitations under the evaluation license...at least they are so kind of informing you this in the first place), and my users were working with truncated data...-:( <br />
<br />

<blockquote>
Which is why I posted above suggesting you use the Wizard and override the data types. 
</blockquote>
FYI-There is no such an option when linking to an Excel file (XLSX).<br />
<br />
Actually I ended up using CSV, where I was able to select correct datatypes.<br />
Was stuck with some side issue regarding the use of CSV file (as posted above), however got pass that as well..<br />
<a href="https://www.experts-exchange.com/questions/29127862/Remove-timestamp-from-file-name.html?anchor=a42748043&notificationFollowed=219255602&anchorAnswerId=42748043#a42748043" rel="ugc">https://www.experts-exchange.com/questions/29127862/Remove-timestamp-from-file-name.html?anchor=a42748043&notificationFollowed=219255602&anchorAnswerId=42748043#a42748043</a><br />
<br />
Therefore just waiting for users confirmation in order to close this thread.<br />
<br />
Thanks,<br />
Ben
</div>


<div>
&gt;&gt; FYI-There is no such an option when linking to an Excel file (XLSX).<br />
<br />
Yes, I know. That comment was in reference to Importing the data, not linking to Excel.<br />
<br />
&gt;&gt;&nbsp;Actually I ended up using CSV, where I was able to select correct datatypes.<br />
<br />
Would like to see the data definition &nbsp;:)
</div>


<div>
@Mark,<br />
See attached.<br />
FYI- This is from the latest CSV I'm dealing with for now...<br />
Thanks,<br />
Ben<br />
<a href="https://filedb.experts-exchange.com/incoming/2018/12_w49/1406296/1.txt" target="_blank" class="file-inline" title="1 (4 KB)"><svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 512 512"><path d="M67.508 468.467c-58.005-58.013-58.016-151.92 0-209.943l225.011-225.04c44.643-44.645 117.279-44.645 161.92 0 44.743 44.749 44.753 117.186 0 161.944l-189.465 189.49c-31.41 31.413-82.518 31.412-113.926.001-31.479-31.482-31.49-82.453 0-113.944L311.51 110.491c4.687-4.687 12.286-4.687 16.972 0l16.967 16.971c4.685 4.686 4.685 12.283 0 16.969L184.983 304.917c-12.724 12.724-12.73 33.328 0 46.058 12.696 12.697 33.356 12.699 46.054-.001l189.465-189.489c25.987-25.989 25.994-68.06.001-94.056-25.931-25.934-68.119-25.932-94.049 0l-225.01 225.039c-39.249 39.252-39.258 102.795-.001 142.057 39.285 39.29 102.885 39.287 142.162-.028A739446.174 739446.174 0 0 1 439.497 238.49c4.686-4.687 12.282-4.684 16.969.004l16.967 16.971c4.685 4.686 4.689 12.279.004 16.965a755654.128 755654.128 0 0 0-195.881 195.996c-58.034 58.092-152.004 58.093-210.048.041z"/></svg>1.txt</a>
</div>


1.txt

<div>
Hi Experts,<br />
<br />
While trying to do the above, I have fallen into another trap...please rescue me!!<br />
<br />
<a href="https://www.experts-exchange.com/questions/29128549/Error-running-update-query-after-changing-from-XLSX-to-CSV.html#questionAdd" rel="ugc">https://www.experts-exchange.com/questions/29128549/Error-running-update-query-after-changing-from-XLSX-to-CSV.html#questionAdd</a><br />
<br />
Thanks,<br />
Ben
</div>


<div>
Hi Experts,<br />
<br />

<blockquote>
Access reviews the first eight rows in each column to suggest the data type for the corresponding field.
</blockquote>
Currently I am stuck with this project, as whichever I turn there are heavy bumps on the road...<br />
<br />
Since CSV turns to be problematic as well, I thought of an idea to stay with Excel and finding a way to force the wizard to recognize those long fields as &quot;long text' as follows.<br />
<br />
Will create a column named Sort by (yes/no) and then add some dummy records there with long text on those columns I need to be mapped as long text, and have this sort by that column...<br />
<br />
What do you say for that?<br />
<br />
Thanks,<br />
Ben
</div>


<div>
Ben,<br />
<br />
I know I mentioned this at least once in this or one of the other threads on this topic. &nbsp;Have you created a staging table that you can import the data into, rather than linking it? &nbsp;If you do this, you can define the fields with the appropriate data types or define them all strings except for those that need to be memo?<br />
<br />
If you create the staging table with field names identical to those in the import file and fields defined as the appropriate data type, you set yourself up for potential import errors (if someone has entered a string in a numeric field) in Excel. &nbsp;But if you setup all of those fields as strings, except those that need to be memo, then all of the data will import into this staging table. &nbsp;When I do this, I generally add several fields to the end of the table (AN - Autonumber, Flag - Y/N, ImportComments-text). &nbsp;Since these are at the end of the table, when the the file loads, the autonumber fills in appropriately, and the other remain blank or null (configure them the way you want).<br />
<br />
This allows me to run a series of queries against the data in the staging table to determine whether all of the data is of the appropriate type (and also value for those fields that belong to lookup tables). &nbsp;I run through this set of queries setting the Flag to True and the Comments to some Description for each error found. &nbsp;Then I present those errors to the user to fix (or allow them to simply print a report so that they can fix the data in the Excel file). &nbsp;Finally, when I am done with that I provide a way for the user to import all of the data into the appropriate fields in the production table, using the appropriate conversion function to convert the string value to numeric or other data types.<br />
<br />
HTH<br />
Dale
</div>


<div>
Hi Dale,<br />
<br />

<blockquote>
Have you created a staging table that you can import the data into, rather than linking it?
</blockquote>
<br />
Currently we have data stored on the web (under Caspio) and there we have many tables, I only import them into Access in order to printout a report and keep track which were already printed.<br />
<br />
The existing process is very simple, Caspio exports them to a variety of formats (Access, Excel, CSV and XML), then we have links to those exported files as tables, and running append queries will store them into local Access tables.<br />
<br />
If I have to change the process and start reading those files by code, it will take significant programming time.<br />
<br />
Therefore would prefer a solution that will keep the process flow as is, just fix those issues.<br />
<br />
I understand there are other advantages of using the staging table, however can only work on issues we are currently facing (for the time being), perhaps at a later time will get to enhance this as well.<br />
<br />
Therefore would focus primary on being able to overcome the Excel 255 limitation.<br />
<br />
Thanks,<br />
Ben
</div>


<div>
Hi Experts,<br />
<br />
While trying to work on the above solution, to export to Excel some records (at least one record) with large data, which will force Access to map those columns as long text, I'm facing the following obstacle...<br />
<br />
There is no way I can select the order of the records to get exported.<br />
<br />
Therefore I have the following question, does someone know of a way to change the order of an Excel sheet by given column (thru code)?<br />
<br />
Thanks,<br />
Ben
</div>


<div>
Hi Experts,<br />
<br />
At this point I think the best (easiest) way to go here is to avoid linking to Excel, just use CSV as linking file, and there a have a way of mapping it, while for the other issue I had with CSV, that cannot run update queries against it, I will have to delete those records and re-import, thereby avoiding having to use any update query...<br />
<br />
Thanks,<br />
Ben
</div>


<div>
Well i encountered this issue lately similar so here is what i found:<br />
Lets assume that you have a Column named Status and you have in the cell<br />
Status<br />
1<br />
2<br />
3<br />
Unknown<br />
4<br />
Unverified<br />
<br />
When you link the Excel to Access you would probably think that Access would read the column and imports it as text...wrong...Access will read the 1st cell &nbsp;--&gt; 1 ( i assume the 1st row is treated as Field) and decides that this is a numeric field despite the text in the cells below...(it would just display an Error placeholder...i can't remember what it was).<br />
So in your case ...if...its a quick and dirty solution...(probably too dirty) ...if you pad your cells (the 1st which contains the data ) with lets say 255 spaces ..or dots...or whatever...Access will read the Cell and decides its a long text....just tested it and its working...
</div>


<div>
@John,<br />
Right that will work, however I cant use it as this will require either users change that file manually every time we get a new file (a couple of times per day...) or I enter new line by code (which I've mentioned above similar approach, of sorting by code.<br />
Thanks,<br />
Ben
</div>


<div>
I faced the same kind of an issue with EXCEL files.<br />
I exported each file to CSV, then imported the text file - each line as one text record<br />
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;Line Input #1, Temp &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; <br />
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;Names = Split(Temp, &quot;,&quot;)<br />
Names is an array containing each field of my data. I can now examine each element of Names and process it.
</div>


<div>
<div class="content wysiwyg-content">
Hi Experts,<br />
I need to link an Excel file to my Access application, however realized that most of the fields are being defined as short text (255) after being linked thru the wizard.<br />
Now this is causing trouble as fields with longer text are being truncated, and I don't see a way of being able to change these mappings.<br />
Any (easy) suggestion?
</div>
</div>


Hi Experts,
I need to link an Excel file to my Access application, however realized that most of the fields are being defined as short text (255) after being linked thru the wizard.
Now this is causing trouble as fields with longer text are being truncated, and I don't see a way of being able to change these mappings.
Any (easy) suggestion?

Mapping Excel fields when linking to Access app.

Microsoft Office is an integrated suite of applications that includes Outlook, Word, Excel, Access, PowerPoint, Visio and InfoPath, along with a number of tools to assist in making the individual components work together. Coding within and between the projects is done in Visual Basic for Applications, known as VBA.

Microsoft Office

Microsoft Access is a rapid application development (RAD) relational database tool. Access can be used for both desktop and web-based applications, and uses VBA (Visual Basic for Applications) as its coding language.

Microsoft Access

Microsoft Excel topics include formulas, formatting, VBA macros and user-defined functions, and everything else related to the spreadsheet user interface, including error messages.