Other than an extra space after the last comma, I see nothing wrong with what you show
Code:
DoCmd.OpenForm "Create Model Portfolio Form", , , , , , "ABC:XYZ"
Private Sub Form_Open(Cancel As Integer)
Dim inputinfo As String
inputinfo = Me.OpenArgs
End Sub
If written as ...OpenArgs() that is how you write a function named OpenArgs, which would be incorrect.
Suggestions:
1) create 2 new forms frmOne with only a command button and frmTwo with nothing. Create a button event to open frmTwo with open args of "Hello" and replicate the form open event for frmTwo with a message box: Msgbox Me.OpenArgs. If you save both, close frmTwo and click button and frmTwo opens and you get the message, your other opening form may be corrupt. I'm assuming your posted code is exactly the same as the real code. It is best to copy and paste code AND use code tags (# on forum menubar). Not only is tagged code easier to read, bad things can happen to long lines of code when not used.
2) if corruption is suspected, create a new form (or use frmTwo) and try copying/pasting all the controls from old to new.
3) post a zipped copy of your db for examination
4) adopt a proper naming convention and eliminate many of the problems associated with what you're now doing. Create Model Portfolio Form is too long but worse, contains spaces. I suspect you have object names with special characters somewhere as well (-,*,%,$,# etc.) See
Naming conventions - http://access.mvps.org/access/general/gen0012.htm
https://www.access-programmers.co.uk...d.php?t=225837
What not to use in names - http://allenbrowne.com/AppIssueBadWord.html