Tracy Thanks

I needed a quick and dirty so I ginned this up this morning. You have a much more thorough approach to notes and we will need to be getting there some day.

I wrote a lengthy description how I handle both canned policy notes that are generated when a user take an action against that policy ( cancellation, endorsements, collection problems, audit problems.) and when I went to hit the send button I lost all of it. It is Christmas party time at my client's tonight so I do not have the time to rewrite it all. Dang I haven't done that in a long time.

Maybe someday we can get together at a conference and discuss some of the trial and tribulations of WC insurance. It would be refreshing for me as I get absolutely nothing from the client in the way of spec. The spec for the AR system was we need to have a AR system or we need a commission system. From that I developed what I thought would work best. The fact that prior to my VFP consulting life, which began when I retired, I worked on many system as a CPA has helped a lot, but it would be nice to see or talk to someone who has developed something different.

Thanks again for your response
Very refreshing
Gaylen






>I too work in the insurance industry and we handled notes slightly different. Our main form has a pageframe that covers about 2/3rds of the form. On it are two pages. The 1st tab is a huge edit box that we use to display important messages (Cancellation processing, etc). The 2nd tab is labeled Activity List which is a grid that contains notes. There is a button that jumps to the profile for that policy's note in the grid. The grid display all notes pending action either open or urgent. It includes the fields: CSR, Refer To, Date, Follow Up Date, Subject, Message, and Status. The Status options are Open, Closed, and Urgent. There is a drop-down list that allows the user to filter which notes they want to view (Open which is visible only if the user is the user in the Refer To field or Urgent which all users see). We have an option under setup which also allows the user to elect to show all pending notes when they go to a specific profile if any notes are still open or urgent.
> When the user displays that profile and there are open or urgent notes a popup window displays the notes and it must be closed before the profile (insured, policies, accounts, etc) can be seen. Entering/viewing notes is available on any profile page from a button on the toolbar as well. there is also a report that lists all open or urgent (or both) notes that can be filtered or sorted by date or policy or profile or name.
>
>
>
>>Thanks Terry
>>Yes it is needed for eof(). I guess that is because of the phantom record that one needs to deal with. With bof() you don't.
>>
>>I am creating a follow up system for users that put free form notes in the insurance policy notes that require follow up. When they create the follow up note, it is captured along with some other data in a separate follow up table. When they log on each day a screen will come up that is merely an edit box on a form containing all open notes, so the user is forced to review the follow up notes at least on a daily basis. (Mgt requirements this as they have grown so fast and the volume of notes is getting larger and larger and the employees are forgetting they have pending item that require action. Lost a $300,000 policy recently because someone failed to follow up.) As they click through the table the note is displayed in the edit box. Control source for the edit box is the underlying follow up table. That is why the thisform.refresh
>>
>>I looked at your RIO code some time ago and liked what I saw. I will look at this again for the hard assignment you mentioned.
>>
>>Sorry for being verbose, but this client has grown from less than a million in premiums and 1 1/2 employees a little over 2 years ago and is now over 40 employees and is looking at 43 million in premiums this year. It has been like Mr. Toads wild ride.
>>
>>Thanks
>>Gaylen
>>
>>
>>
>>>I think you have to check if the next record is EOF
>>>skip && at last record
>>>if eof()
>>> skip -1
>>>endif
>>>
>>>I can rcall if this a a bof() or eof().
>>>
>>>I noticed you are using thisform.refresh. So I guess you are binding your controls. The best performance (and maximum control) results from hard assignments (IMO):
>>>myform.mycontrol.value=mydbf.fieldvalue
>>>
>>>There is an example, if you're interested, of "hard assigment" performance in download #16575 .
>>>
>>>
>>>>I have an edit box on a form with several controls. One is to move to the next record(NEXT) and the other is to move to the previous record (PREVIOUS). The code in the next button is as follows:
>>>>
>>>>

>>>>Select cursor
>>>>
>>>>If  Eof()
>>>>	Wait Window "Last Note" Nowait
>>>>Else
>>>>	Skip
>>>>Endif
>>>>Thisform.Refresh
>>>>
>>>>
>>>>

>>>>
>>>>When it get to the eof()it will show the last record and the next time you click the NEXT button the edit box is grayed out. Evidently on the phantom record.
>>>>
>>>>Going the other way (previous)and using the same code but using BOF() it stops at the first record no matter how many times you click the PREVIOUS button.
>>>>
>>>>How do I get around the blank(gray) edit box. I know it must be something simple but I need to demo this tomorrow and would like to avoid the gray box.
>>>>
>>>>
>>>>Thanks
>>>>Gaylen