Hi, At April 22, 2017, 10:09 AM, Jiří Činčura wrote:
>> I was starting to suspect that, since the other tables that I was able >> to generate the code for didn't have computed fields. Are there any >> hints that I can use? >> >> I can try to look at the code to see if I can fix the problem. And, >> since I never did look inside the ADO.Net driver code. Can you guide >> me to what would be the area of code that I would need to look at? >> >> I'm willing to try to fix the problem, since this is not the only >> table in that database that has computed fields. > You can create a table without computed field, generate the CF for it. > And then do the same for a table with computed field. But, what could cause it not to recognize those fields properly? Because when I look in the database's system tables, the RDB$FIELD_TYPE and RDB$FIELD_LENGTH both have values in them, one would be VARCHAR(132) and the others would be CHAR(1). -- Best regards, Daniel Rail Senior Software Developer ACCRA Solutions Inc. (www.accra.ca) ACCRA Med Software Inc. (www.filopto.com) ------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot _______________________________________________ Firebird-net-provider mailing list Firebird-net-provider@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/firebird-net-provider
