in the immortal words of Arte Johnson (a reference probably lost on at least 75% of the audience of this post due to age) "Very Interesting"!
In an attempt to figure out why you are seeing the behavior you are seeing, I thought "maybe" there was a problem with the "offset" calculation for the status_15 field which in your screen shot shows it as 1290 bytes, I figured I take a look at the field name property of the same field in an instance of SL 2011 at my office. This lead to the "interesting" part.
I could not find any fields on the Project Maintenance screen that are currently attached to PJPROJ.status_15. So, I tried inserting a control via customization manager.... strange thing here was that status_15 and status_16 are not available to be inserted. What's really strange here is that the only time fields from a standard table in a screen are not available to be inserted via customization manager is if those fields are already attached to controls on the screen... but like I said, I couldn't find any control attached to that field.... "Very interesting!"
So.... I figured I'd check the Schema documentation in the help files to see if Project Controller uses the status_15 field for something special and maybe that's why it's behaving funny with respect to customization manager....
The help documentation said:
Status_15 - Create invoice drafts from shipper: Y/N
status_16- Shipper invoice method: O = Order Management, B = Flexible Billings, S = no invoice
So at least as of the time that documentation was written these fields are intended to be used for specific functions when certain features are enabled in Project.
So, there is a possibility that there is logic within the Project Maintenance screen that is populating the bPJProj.status_15 "Variable" with something different than what is actually in the same field in the database which would explain the behavior you are seeing.
How exactly did you get these check boxes to appear in the screen? Did you add them through customization manager or did you turn on a feature in one of the project setup screens that made the fields visible?
If you added them through customization manager then here is what I would recommend as a way to help diagnose exactly what is happening:
1) remove the check box control by deleting it in customization manager
2) save the customization
3) close and reopen the screen
4) Add a text box control to the screen via customization manager attached to the PJProj.status_15 field and make sure the mask for the control is set to a capital 'M'
4.5) You might need to add a "Call dispfields()" call in customization manager VBA code... maybe in the click event of a button you could add or something to make sure that you know you can force the control to show the current value of the attached variable on-demand
5) navigate to the same set of projects you checked before and see what shows up in the text box...
Alternatively you could also add a little VBA code to the check event on the project ID field that looks something like this:
'***********************************
Dim strStatus_15 as string
call getbuffervalue("bpjproj.status_15", strStatus_15)
Call messbox("The value of status_15 is: " & sparm(strStatus_15), 0, "Debug Code")
'***********************************
then navigate through some projects so you can see exactly what the given variable is being populated with.
Again, hope this helps.
Regards,
Tom Malia
T&T Data Solutions L.L.C.
