So long as the elements are bound to the same fields of the database, it should be the same. But you can also display and hide elements of the form depending upon the user using If @UserID ( ) command. You can also make the group of users and define there access accordingly. The same form can look and work different for different users. You can also have individual element behaves different for different users.

I have divided users into different groups here:

//Code on Form Entry

If UDF_LevelOneCheck () = "Passed" then
	{

		//Visibility (PastVisits RW, 1)
		Visibility (PastVisits RB, 1)
		Visibility (Tracker, 1)
		Visibility (Est_Data, 1)
		Visibility (SelectVisit, 1)
		Visibility (AddNote, 1)
		Visibility (IMM_Record, 1)
		Visibility (PrintRecord, 1)
		Visibility (Activity, 1)
		Visibility (DocManage, 1)
		Visibility (NCPDPID, 1)
		Visibility (Pharmacy, 1)
		Visibility (Panel Feedback, 1)
		Visibility (MakeClientR, 1)
		Visibility (Client, 1)
		Visibility (SendLetter, 1)
		Visibility (Activity Report, 1)
	}

	Else
	{
		//Visibility (PastVisits RW, 0)
		Visibility (PastVisits RB, 0)
		Visibility (Tracker, 0)
		Visibility (Est_Data, 0)
		Visibility (SelectVisit, 0)
		Visibility (AddNote, 0)
		Visibility (IMM_Record, 0)
		Visibility (PrintRecord, 0)
		Visibility (Activity, 0)
		Visibility (DocManage, 0)
		Visibility (NCPDPID, 0)
		Visibility (Pharmacy, 0)
		Visibility (Panel Feedback, 0)
		Visibility (MakeClientR, 0)
		Visibility (Client, 0)
		Visibility (SendLetter, 0)
		Visibility (Activity Report, 0)

	}

If UDF_LevelOneCheck () = "Passed" then
	{
		ReadOnly (IHCExempt, 0)

	}
	Else
	{

		ReadOnly (IHCExempt, 2)
	}



If @Mode () = 1 and UDF_LevelOneCheck () <> "Passed" then

	{

		Readonly (Chart, 2)
	}
	Else
	{

		Readonly (Chart, 0)
	}
 

You many also use #include files to avoid duplicating much programming.