This question is locked. New answers and comments are not allowed.
I have several stored procedures whose parameters have " = NULL" or " = 0" or some such thing after them in the sproc declaration. Yet when OpenAccess reverse-engineers the stored procedures into a calling method, it does not use nullable types to represent those parameters (such as short? or int?). It instead uses non-nullable types (e.g. short or int) and then I'm faced with having to go through and correct them all, or set and cast them in the caller, etc. Why can't OpenAccess see that they're nullable and represent them accurately?
There also seems to be an issue with mapping the CHAR(1) data type, which OA maps as "string" and again I have to manually fix it or cast it.
There also seems to be an issue with mapping the CHAR(1) data type, which OA maps as "string" and again I have to manually fix it or cast it.