Novell Server - Records Crossover

[Tom Cone Jr]

Re: Novell Server - Records Crossover

Manny, the autoincrement field rule looks to the record in your table that has the highest order number and then increments it. In a multi-user setting, if two workstatioins begin a new order at about the same time, the field rule on each machine will find the SAME highes field value, since no new records have been saved to your table. Question 1 for you: Do you have questions about this?

Next, Alpha displays the incremented order number on your form. Until that record is commited to the table it's only a provisional order number. If the other workstation saves their record to the table first, then this work station's field value will be checked against the table when its order is commited. If it's no longer highest, it will be incremented again. Question 2 for you: Do you have questions about this?

Next, the display of detail records from your linked one to many child table is "crossing over" because the two workstations have, at least temporarily, the same auto-incremented order number. The overlap goes away when the second workstation saves their record, because the just saved record now has a different order number. Handled transparently for you by the field rule. Question 3 for you: Do you have questions about this?

Suggestions to prevent the display of child table records entered on other workstations in a multi-user setting:

a) Force each new order to be immediately saved. This commits the record to the table so the next workstation's field rule will compute a DIFFERENT order number. Use this approach if you must use the autoincrment field rule.

b) An alternative that will work if you must use the autoincrmenet field rule is to suppress the display of the linked child table records on your form until you've saved the order header. If you do it this way you don't need to force the newly begun header record to be saved first.

c) An alternative that many prefer is to NOT use the autoincrmenet field rule, but to roll your own incrementing script that fires when the parent table record is saved. Sample code has already been posted here. This typically involves retrieving the last order number from a table OTHER than your order header table, and then immediately commiting a newly incremented field value to that table. This works well if it's done when the order header record is saved, and before you try to begin entering linked child table records.

Last question: Do you have questions about these ideas?

[NancyL]

Re: Novell Server - Records Crossover

Thanks to all....and just to clear things up...I would never yell at Manny....I know better....
We've been working together for 15 years!

I need to get more attention and boy I got it!

We've tried to save the record as soon as we start however there are several fields in the header that need to be completed before we can save the record. Buy the time we complete the fields I can see the other user parts.

Next?

[Peter.Greulich]

Re: Novell Server - Records Crossover

We've tried to save the record as soon as we start however there are several fields in the header that need to be completed before we can save the record. Buy the time we complete the fields I can see the other user parts.

Next?

Hhhmmm...

What if you hide the child browse until the header is saved?

or

You could have the header form based upon the table only. When the header is saved, auto-popup a form based upon the set, or child table - either one w. the browse.

Really, there are a million ways to do this (I'm exaggerating only slightly).

[Peter.Greulich]

Re: Novell Server - Records Crossover

P.S. Also, (don't take offense) you have missed the point of saving the header record 1st (programmatically) then filling in the remaining fields after the fact.

[jkletrovets]

Re: Novell Server - Records Crossover

I would never yell at Manny....I know better....

It's not Manny I was talking about :) Your tone using ALL CAPS like in message 27 will not motivate people here to help you IMHO. It is important to note that this is a peer supported board and is not an "Official Alpha" support system. The people on this board are donating their time.

We've tried to save the record as soon as we start however there are several fields in the header that need to be completed before we can save the record.

Forget about using the built in field rules for fields being required and roll your own field rules that are implemented at the appropriate time (when you leave the header section)- this eliminates any issue you have as far as saving the header first with it's unique id field. This is the most straightforward way to accomplish your end goal......in my opinion at least.

[jkletrovets]

Re: Novell Server - Records Crossover

In case you want to go the way I mentioned above. Here is another function I wrote to check for a required field. It can be placed right before you leave the header section - just use it for each field you want to be required. Example - if you have 4 fields to check to be required - then you would use this function 4 times.

'Date Created: 29-Aug-2006 02:14:11 PM
'Last Updated: 14-Feb-2007 07:40:47 PM
'Created By  : Jeff
'Updated By  : Jeff Kletrovets

FUNCTION Reqd_Fld_Check as L (FldToCheck as C)
	'****** Place this function in the OnPush event of the Save Button ************
' ****** Sample Required Field Checking - OnPush event of Save Button
'IF Reqd_Fld_Check("empidf")=.F. then
'	topparent:empidf.activate()
'stop
'end if
' ***** End of Sample Code for Required Field Checking
	DIM TblReqd as P
	DIM FldReqd as P
	TblReqd = table.current()
	fldreqd = TblReqd.field_get(fldtocheck)

	' If table is in Enter Mode then we need to perform the check for an empty field.

	SELECT
		CASE tblreqd.mode_get() = 2
			' ************* ENTER MODE *********** Enter Mode = 2
			IF fldreqd.is_blank() THEN
				' ********  Now get the Default Descrptive Name to display in the message box.
				'This will make this function dynamic by displaying the default descriptive name in
				'the message box.
				'Getting field name here
				fldlong = tblreqd.field_get(fldtocheck)

				'If the table has rules get the default descriptive name which is long_name
				IF fldlong.has_rules() THEN
					rules = fldlong.rules_get()
					long_name = rules.Long_Name
				ELSE
					long_name = "Data Entry"  'use this as default text in message box if no rules
				END IF

				' *********** End of Get Default Descriptive Name *********
				' ***********  Now show error message box ***************
				ui_msg_box("Required Field","The "+long_name+" field must be filled in!",UI_STOP_SYMBOL)
				Reqd_Fld_Check = .F.
'				vcommand=eval("fldtocheck+'.activate()'")
'				evaluate_template(vcommand)
'				return						
'				end
			ELSE
				'Field has data entered so it is ok to move on
				Reqd_Fld_Check = .T.

			END IF

		CASE tblreqd.mode_get() = 1
			' ************* EDIT MODE *********** Edit Mode = 2
			IF fldreqd.is_blank() THEN
				' ********  Now get the Default Descrptive Name to display in the message box.
				'This will make this function dynamic by displaying the default descriptive name in
				'the message box.
				fldlong = tblreqd.field_get(fldtocheck)

				'If the table has rules get the default descriptive name which is long_name
				IF fldlong.has_rules() THEN
					rules = fldlong.rules_get()
					long_name = rules.Long_Name
				ELSE
					long_name = "Data Entry"
				END IF

				' *********** End of Get Default Descriptive Name *********
				' ***********  Now show error message box ***************
				ui_msg_box("Required Field","The "+long_name+" field must be filled in!",UI_STOP_SYMBOL)
				Reqd_Fld_Check = .F.
'				vcommand=eval("fldtocheck+'.activate()'")
'				evaluate_template(vcommand)
'				return
'				end
			ELSE
				'Field has data so it is ok to move on
				Reqd_Fld_Check = .T.

			END IF

	END SELECT
	

END FUNCTION

[NancyL]

Re: Novell Server - Records Crossover

THANK YOU JEFF....opps just kidding thank you Jeff and to all of you.

Didn't mean to yell......

You all seem to understand how important required fields are. These users will pass over anything they're allowed to.

Jeff Manny is going over what you sent and seeing what he do with it.

Thank you and I'll be back!!!

[jkletrovets]

Re: Novell Server - Records Crossover

Sure thing....for my function to work properly you just have to fill in the "Default Descriptive Name" in the Field Rules for the table. The function will go get that name and then let the user know which field is required by name.

For example, if a field is not filled in then the function will pop up a message that says something to the effect of:

"The Customer ID field is Required"

Where Customer ID is the default descriptive name for the CUSTID field.

[Peter.Greulich]

Re: Novell Server - Records Crossover

Nancy,

Attached is a very simple example of saving the header record first. Try this on your network. Have two or more users start a new record at the same time and enter a bunch of child records. See if this doesn't work for you. Have Manny the Programmer look at the code in the two buttons - it's trivial!

Try it! What the hell. It might actually work for you!

[manny]

Re: Novell Server - Records Crossover

Thank you Tom! I have used your idea of hiding the child table. In so doing, I have added a button called 'New Item' and the following code and it works fine:

if Invoice_header->Ordered_by <> "" then
Orders:browse1.commit()
browse1.new_record()
end if

Thank again.

Manny

[joannristau]

Re: Novell Server - Records Crossover

Hi Nancy,
I just wanted to reply to your question regarding Novell servers :

"Is there a downside to using Alpha5V9 on Novell versus Windows 2003 server"

In a nutshell, no. My current employer, and previous employer, run our A5 apps from a Novell server without issues, and work very well. In fact, I far prefer Novell over Windows, just because its so solid.

Best wishes to you on your application development.