Normal Topic strange occurrence with application (Read 780 times)
Wilder
Member
*
Offline



Posts: 25
Joined: Jun 11th, 2015
strange occurrence with application
Jul 22nd, 2015 at 7:17pm
Print Post Print Post  
Hi All.

I have just finished working on a insurance agency policyholder/ policy management. 
Every things works fine on my pc.  I installed the application on the end users pc and everything goes crazy

The forms use subforms main form is Policy Holder, subform has basic policy information, Clicking on the Policy Number in the subform opens the Policy form with all information on the policy.  My PC work correctly.
On end user PC the click of policy number of subform may bring up the correct policy, I may bring up one of the policies for the Policy Holder or it might bring up a policy form the first person in the file.  It has started at the first policy for that person and just worked its way through the list for that person, doesn't mater which policy you click on .

Has anyone had this kind of thing happen.

I'm suspecting bad memory in clients PC.

Foye.
Wilder's Software
  
Back to top
 
IP Logged
 
Wilder
Member
*
Offline



Posts: 25
Joined: Jun 11th, 2015
Re: strange occurrence with application
Reply #1 - Jul 22nd, 2015 at 7:57pm
Print Post Print Post  
Further testing on my pc finds that is works in preview mode but not in live mode.
  
Back to top
 
IP Logged
 
Wilder
Member
*
Offline



Posts: 25
Joined: Jun 11th, 2015
Re: strange occurrence with application
Reply #2 - Jul 22nd, 2015 at 10:42pm
Print Post Print Post  
found the problem.

Needed to add a xresultsetclose after record retrieved.

would be nice if preview functioned the same as live db.

  
Back to top
 
IP Logged
 
Ray the Reaper
Global Moderator
Members
Lantica Support
*****
Offline


The One & The Only

Posts: 2482
Joined: Aug 20th, 2003
Re: strange occurrence with application
Reply #3 - Jul 23rd, 2015 at 1:54pm
Print Post Print Post  
Preview and Runtime function exactly the same. You may have just not seen the issue in Preview mode if you were working with a limited data set.

I am not sure how an XResultSetClose() is going to affect which record is retrieved ever. But it is very important to always close every XRS that you open otherwise you can be left with locked records especially in Client/Server setups.

-Ray
  

Raymond Yoxall Consulting
ray.yoxall@gmail.com
ryoxall@lantica.com
Sesame Applications, Design and Support
Back to top
IP Logged