Avoiding Type Coercion Issues
One of the most challenging aspects you’ll find in automating your web application is avoiding type coercion issues. Access client is generally correct when it needs to guess the data type of a value in a control used in a user interface or data macro. When you’re viewing your web forms in a browser, however, Access Services does not always follow the client behavior. You might find that your macro actions on web forms function exactly the way you want when you work with the form in Access client, but the same macro actions result in different behavior, perhaps even displaying runtime error messages, when you work with the same web form in a browser.
In general, if you have a web form control bound to a field in a ...
Get Microsoft® Access® 2010 Inside Out now with the O’Reilly learning platform.
O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.
