VFP 7.0 and ASP.NET

Hot Topic

foxpro2.5 application migration from windows98 to XP (Urgent)
Runnning VFP6.0 in Win 2003 server
How to tell if cancel was clicked in the print dialog.
Convert month to numeric
a bit of array related confusion
Cancel Button Does not work--A known bug?
Setting papersize in Crystal Report from Foxpro
MS XML parsing - problem
pulling data from one field and making a new column out of it
forms

Visual FoxPro

VFP 9.0 SQL worthless under a non client server network?
show certain record in gridbox
Path settings in Environment Manager
VFP
Improved memo fields in grids
return from a form.
Grid objects problems/questions
ODBC & text to columns
FoxPro character fields in .Net showing as blank strings.
Inserting and Updating images file from VFP9 to SQL Server 2005

VFP 7.0 and ASP.NET

Friends,

I developed an application with VFP7.0 and ASP.NET . Every thing is going good except one problem.

Once in a while application is crashing when I am executing sql statements and it is giving error like "Object Reference not set to an instance of an object". I tested the connection status and it is good.

I am thinking that, it is happening due to some Record Locking mechanisms. My application is intranet application.

I didn't set any settings to the database like MultiLocks --- ON or so...

My question is -- Do I need to set any settings to avoid these interlockings and crashing the application

Can any one help me please

Thank you.

Answer this question

VFP 7.0 and ASP.NET

  • Björn

    Hi CetinBasoz,

    I know that this message has nothing to do with VFP itself. But, when I am executing the querry , for example, executeReader or DataAdapter.Fill method, it returns the datareader or dataset. Since Problem is giving when executing the command, it is giving the mentioned error(Object Reference not set to the instance of the object).

    Only once in a while this error is coming and the application is crashing eventhough I handled all exceptions. At that moment, I have to recycle my Worker Process to make application work again.

    I tested the SQL Statement separately and it is executing good.

    So, I am thinking that due to some record locking mechanisms it is happening. May be at the same time , two users are updating the same row.

    I don't know how to control this. Any Idea

    Thank you.

    Sri.

  • Glenn LaVigne

    That message has nothing to do with VFP itself. On the other hand it's a popular message for ASP.Net. There might be a lot of reasons for that. Here in your case what comes to mind is ASP.Net session is timing out.
  • VFP 7.0 and ASP.NET
Answer this question