I would assume LOC is completely irrelevant for your purposes is you didn't write any visual basic code for an office program project. LOC is used to measure effort, and if you were to use the LOC involved in the construction of access itself, the value is obviously 0 because it takes zero effort to install access. understand?
as far as any objects that you see through the interface in access, I'd have no idea how you would measure stuff like that. probably measure it by the amount of time it took you to click around and create the project as it is now? what other way do you have?
LOC is incredibly inaccurate as it relates to macro objects because, if you use the interface option to convert any given macro to visual basic code, the code that you see as a result is canned code that probably came from the mind of a lower-level software engineer at Microsoft anyway. Or even more plausible, the code associated with macros has probably remained the same since the 1990s anyway.
but just to entertain you and myself (), if you want the properties associated with any given form that you have in an access database, put this code in a visual basic module, press Ctrl+G to open the debug window, then press F5 to run the routine and see the printout:
Code:
function print_props()
dim prop As dao.property
for each prop In forms("YOUR FORM NAME").properties
debug.print prop.name
next prop
end function