Issue 107207 - Optional field in mdb left blank fails (cannot be saved)
Summary: Optional field in mdb left blank fails (cannot be saved)
Status: UNCONFIRMED
Alias: None
Product: Base
Classification: Application
Component: code (show other issues)
Version: OOO310m11
Hardware: PC Windows XP
: P3 Trivial (vote)
Target Milestone: ---
Assignee: AOO issues mailing list
QA Contact:
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-11-25 16:40 UTC by sanyock
Modified: 2013-01-29 22:01 UTC (History)
1 user (show)

See Also:
Issue Type: DEFECT
Latest Confirmation in: ---
Developer Difficulty: ---

Attachments
sample files (4.21 KB, text/plain)
2009-11-25 18:36 UTC, sanyock 		no flags Details
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this issue.
Description sanyock 2009-11-25 16:40:57 UTC 
I connected OOBase to an MS Access MDB file created from ODBC manager. 
Everything seems working fine except optional fields. I was able to design a 
database structure. But when editing a table data it does not let me leave an 
optional long integer blank. 

Would anyone please suggest how can this be fixed? 

Note: optional text fields work as expected
Comment 1 sanyock 2009-11-25 18:35:29 UTC 
It actually seems to be another problem: OOBase does not save 
"optional" (nullable) attribute for a field.
I reopened the database in the designer and fields are "required" again though 
I marked them as "not required".
Trying to save them as "not required" does not help.
The files have been attached.
Comment 2 sanyock 2009-11-25 18:36:24 UTC 
Created attachment 66346 [details]
sample files