MSAccess 2003

L

Larry Linson

wgrasty said:
Does anyone know if there are plans for an SR to fix the following problem
in
MSAccess 2003 and if so when:

http://support.microsoft.com/kb/824159

If not, any other workarounds besides what Microsoft suggests?
Click to expand...

We are not Microsoft employees, here, and do not speak for Microsoft. As
for corporate plans, release dates, etc., that is not something they
typically share with us (in re: do we know about SR Plans).

Best regards,

Larry
 
S

Scott Lichtenberg

I've never run across this one personally, and I don't know what MS's plans
are for a fix, but you might try updating your records through code rather
than through a query. You can access the remote data source through ADO and
use the execute method on the connection or a command object. I've never
had an issue with ADO or ODBC. As a worst case scenario, you can write a
function that opens a recordset and loops through it updating as necessary.

Hope this helps.
 
W

wgrasty

Any idea where I can go to get that answer without paying $100 to do so? MS
referred me to the forums.
 
K

Klatuu

I know of no other work around. The proposes solution is not that
difficult. Just create a table with the structure you need. Then in your
procedure, run a delete query to delete old data that may still be in the
import table, import the text file into the table and run your append or
update query against this table. I would also suggest you create an import
specification for the file to ensure you get the data types correct.

Notice I did not suggest a make table query. I avoid them because the don't
always get the field data types correct and they are serious contributors to
database bloat.
 
A

a a r o n . k e m p f

wow.. that's just classic.

I think that the main workaround is 'keep your data in a database' and
if you _NEED_ to keep it in a text file, write it to the text file on
a scheduled basis.

a text file is not a database.

-Aaron
 
Top