(OKAY, sounds like a washing machine orĪ dish-washer doesn't it) In my mind, what aaj23 has said is probably true. Meanwhile, I have resorted to 1) dumping the files from SQL to text (CSV), 2) importing them (which is actually just the hard way - SSIS is the easy way but if you do it the hard way first and then save it, SQL writes the SSIS script for me theįirst time around - see Kalman's solution above) and then 3) export the data back to Access using a job schedule from SQL (yep, Access not Excel - it is a bit faster). I wish I knew what "IT" is as that is actually the answer I am looking for.
FLEXISIGN 12 IMPORT FILE CRASHES PROGRAM 64 BIT
If we load a 64 bit driver as the user suggested ( )Īnd we attempt to connect a 64 bit accdb/xlsx - so, this would mean that 64 bit office is actually a 32 bit office (single thread apartment)? Can anyone understand why this is confusing? (subtle tongue in cheek)Īdditionally, having hit this 32 bit / 64 bit barrier, time and time again, and given the nature of the beast, I have had to learn "many" new methods (emphasis on the word "many") to cope with the situation and I am here now because I have just toldĪ customer that his project of two years, has gone out of scope and I can no longer continue to work on the issue as he knows it - instead he must drag himself into the 21st Century.
Yet, I am a bit confused by this (reference to aaj23's comment that MS has no intention of supporting 32 bit ).
All well and good if you are without any need to support 32 bit.
0 kommentar(er)
