Duplicate of bug #37757.

Note:

This is not about 'retrieving' data, or limits for data fields, this is about a limit in executing SQL statements directly through a COM(ADODB.Connection) to an Access .mdb file.

Example:

INSERT INTO users (first_name, last_name, address, city, state, zip, username, password) VALUES ('Jonathan', 'Macintyre the 3rd', '123456789 Somewhere in the United States', 'Idaho', 'ID', '12345-12345', 'jonathanmacintyrethe3rd','thisismypassword')

The above command will fail because it is greater than 255 chars. 

The command below will succeed however, using the exact same type of connection:

INSERT INTO users (fname, lname, address, city, state, zip) VALUES ('Jon', 'Mac', '123 US St.', 'Idaho', 'ID', '12345','jmac','1234')

Do you see what I mean? This is the same limitation imposed if you try to create a module in Access with a 'RunSQL' command as the parameter...the field is limited to 255 chars.

However, the first command greater than 255 chars will succeed if you connect through an ODBC (DSN) connection. I am not sure whose limitation this is at this point? Since php is making the connection and call to both, I was guessing that this is a php problem.

Thank you for this bug report. To properly diagnose the problem, we
need a short but complete example script to be able to reproduce
this bug ourselves. 

A proper reproducing script starts with <?php and ends with ?>,
is max. 10-20 lines long and does not require any external 
resources such as databases, etc.

If possible, make the script source available online and provide
an URL to it here. Try to avoid embedding huge scripts into the report.

No feedback was provided for this bug for over a week, so it is
being suspended automatically. If you are able to provide the
information that was originally requested, please do so and change
the status of the bug back to "Open".