Not sure about the function --MS Access

[mks123]

Hi frnds,

Is this custom function which created by user?? the reason I'm trying to figure out ,in one database this below line work but other Database it's not.

CurrentDb.Containers(1).Documents("UserDefined").Properties("Project")

Regards,
mks

[ranman256]

they created an object , like a filter, or an object grouping.
Most likely a group to put all tables/queries as a group in the object filter.

[orange]

I agree with ranman. It seems they created some object(s) named "UserDefined" with a custom property "Project" to related things into a structure that can accessed and that will persist.

FYI
?CurrentDb.Containers(1).Name
Databases

On the database where the code works, what does it produce?

[Micron]

I don't get what 'works on one computer but not another' means.
This looks to me like a reference to the built in database property "Properties" but as posted, it doesn't set or get the value. In 2007, you go to the Office button > Mangage > Database Properties > Custom tab. "Project" is one of values in the Name list. I've not seen that syntax before though, so I'm not sure what Containers(1) is.
The usage might be like

Msgbox CurrentDb.Containers("Databases").Documents("UserDefined").Properties(strPropertyName).Value

[mks123]

thanks for all response.

Is there anyway to delete exist custom property Or first get all list and then delete.?

I use below line but it doesn't work.
db.Containers(1).Documents("UserDefined").Properti es.Delete ("599748")

does anyone has solution.

[mks123]

I have just figured it out. thanks all

sometime I realized how stupid am I.

[Missinglinq]

glad you got it sussed! Forum etiquette dictates when a poster resolves their own problem they post the solution, so that others may benefit.

Linq ;0)>

[Micron]

I suspect it was along the lines of

CurrentDb.Containers("Databases").Documents("UserDefined").Properties("Project").Value = ""

mks123 - please do post the solution as suggested
Thanks.

[ssanfu]

And maybe mark this solved???

[mks123]

Here we go...

I had scenario where I have to update "78945" to 78980 and "4" to "5", so I was deleting with below code which is completely wrong.

With db.Containers(1).Documents("UserDefined").Properti es ''''''Added by Mukesh Yadav
.Delete ("78945")
.Delete ("4")
End With

'''''''''''''''''''''''''''''''''''''''''''''''''' '''''''''''''''''''''''''''''''''''''''''''''''''

Function CreateDbaseProperties()
Dim db As DAO.Database
Dim prpNew As Property


Set db = CurrentDb
 
'''' Delete old property  here it is "project" and "Document number.       
With db.Containers(1).Documents("UserDefined").Properties   ''''''Added by Mukesh Yadav
  .Delete ("Project")
  .Delete ("Document Number")
End With


Set prpNew = db.Containers(1).Documents("UserDefined").CreateProperty("Project", dbText, "78945")  ''''''' you can change "78945" to any number
db.Containers(1).Documents("UserDefined").Properties.Append prpNew
Set prpNew = db.Containers(1).Documents("UserDefined").CreateProperty("Document Number", dbText, "4")     '''''' you canchange  "4" to any number
db.Containers(1).Documents("UserDefined").Properties.Append prpNew


End Function

[Micron]

Why delete properties just so you can recreate them? You change the property value. You don't even have to delete the property value, just change it

[mks123]

really... would you like to show me.

[Micron]

Let's make sure we're on the same page. I mean once you have created a custom property, there's no need to delete it in order to rename it. If you have a situation where you're not sure if a custom or built in property exists or not, the usual approach (for me anyway) is to try to access its value. If you cannot, it generates an error (I forget the error number) so your error trap then creates the property you're trying to access. The end of the trap Resumes, thus whatever you wanted to do after accessing the property gets executed. Typically that is to set the property value. If your code will set it to whatever it already is (assuming there was no error because the property DID exist), then there should be no error in setting its value. This is how I think the routine to set the db ByPassKey property should be attempted - at least that's how I do it.

Do you need a sample for the BypassKey property setting?

[mks123]

yes please!!

[Micron]

This might help you to get a handle on the documents collection & see what you've got defined. I suggest running this to ensure you haven't deleted anything important:

Sub getDocuments()
Dim n As Long

'documents collection is zero based, so subtract 1 from the count
For n = 0 To CurrentDb.Containers("databases").Documents.Count - 1
Debug.Print CurrentDb.Containers("databases").Documents(n).Name
Next

End Sub

The code that follows is how I've done it in the past for the AllowBypassKey property. I suppose you could include the function part within a sub, but for me, when something is going to get called often and has two or more modes, I tend to put it in its own function in a module (library) of functions - helps me to find them as opposed to searching everywhere. Obviously, you would not use the part where the sub manipulates the form, but your own code instead.

Sub SetBypassProp()
Dim db As DAO.Database
Dim prop As DAO.Property
Dim bolMode as Boolean

On Error GoTo errHandler
Set db = CurrentDb
Set prop = db.Properties("AllowByPassKey")

'Note to mks123 - in the sample I'm copying from, I get the user level from my user object and if 'admin'
'I allow this property to cycle, then I change a main form label to red to alert me that it's enabled in case
'I forget to disable it before releasing a new front end
If prop = True Then 'bypass enabled; change it to false
   bolMode = False 'pass this change to the function
   prop = apDisableShift(bolMode) 'property value becomes the function value
   DoCmd.SelectObject acForm, "frmSwtchbrd"
   Forms!frmSwtchbrd.lblVersion.ForeColor = RGB(255, 255, 255)
Else: 'assume prop is false - can only be either true or false
   mode = True 'pass this change to the function
   prop = apDisableShift(bolMode) 'property value becomes the function value
   DoCmd.SelectObject acForm, "frmSwtchbrd"
   Forms!frmSwtchbrd.lblVersion.ForeColor = RGB(255, 0, 0)
End If
MsgBox "Enable bypass is now " & prop 'let admin know the property was changed

Set db = Nothing
Set prop = Nothing
Exit Sub

errHandler:
If Err.Number = 3270 Then 'bypass property doesn't exist so create it
   Set prop = db.CreateProperty("AllowByPassKey", dbBoolean, False)
   db.Properties.Append prop
   Resume
End If

End Sub

Function apDisableShift(Mode) As Boolean
CurrentDb.Properties("AllowByPassKey") = mode
apDisableShift = mode
End Function

Not sure how possible it would be to get stuck in a loop with Resume - never happened to me.
I'll have to play with the user defined property to see how/if I can use this approach - I'm not familiar with that object model or its error trapping. Will try to post something along that line tomorrow.