this error leaves a .ldb file in the database folder, ive fixed this error locally following this guide:

http://www.telerik.com/community/forums/aspnet/editor/invalid-precision-value-inserting-data-into-microsoft-access-memo-field.aspx

however the problem persist on my server, ive updated the .cs class file as suggested, compiled and moved my bin folder overwriting the one on the webserver but i see that the files in the bin folder are not being compiled even if ive changed a class, im not much too sure about this error now, if it is because i cant recompile my class or something else.

When connection to an Access Database, don't use ODBC, but use OleDb instead:

http://www.mikesdotnetting.com/Article/78/AccessDataSource-SqlDataSource-and-connecting-to-Access-databases-in-ASP.NET 

hans_v:

When connection to an Access Database, don't use ODBC, but use OleDb instead:

why?

however it was a server issue, without any modification to the original update accordingly with the link below, it started to work correctly:

http://www.telerik.com/community/forums/aspnet/editor/invalid-precision-value-inserting-data-into-microsoft-access-memo-field.aspx

Elnath:

hans_v:

When connection to an Access Database, don't use ODBC, but use OleDb instead:

why?

Performance

http://www.4guysfromrolla.com/webtech/063099-1.shtml

hello, please explain, how can be faster if it has one more step respect direct ODBC?

> OLEDB sits between the ODBC layer and the application. With your ASP pages, ADO is the "application" that

> sits above OLEDB. Your ADO calls are first sent to OLEDB, which are then sent to the ODBC layer.