Hi

The use of seq.open and seq.close to write some records some time the file itself pops up i mean the files gets open and we can view the records can any body comment why its happening

Thanks

Hi,

What do you mean by "the file it self pop up"? The file opens on the client PC or the baan Server?

- George

can you post the script n the error message

Hi,

The file pops up on client PC itself. We know that seq.open is meant to write some records in text file on backend so that it can be used to create a log fil e or input to other 3rd party software. But some times its opening up physically on client PC.

Thanks and Regards,
mbdave

seq.open is not meant for writing records in a file but for opening a file in different mode.

seq.open is not meant for writing records in a file but for opening a file in different mode.

seq.open can open a file for read, write or append. Sorry, but your comment is completely wrong.

What happens when the file pops-up? There must be a window, I suppose, and what title is in it?

Post your script , that will be helpful for us to find the bug ..

app_start or application.local.start will start a local application if possible ,. E.g. program is writing .txt file and at the end if this file is invoked , using any of above function , it will open a notepad . If on the client the file association is not then for the file u write , the popup may fail. This may explain erratic behavior .

app_start or application.local.start will start a local application if possible

You mean "start.application.local()" ;)

Right Sir. Knew somebody will correct if wrong or people are smart enough to understand it .... :)

Dear friends ,

I know what seq.open and seq.close does i had used that more than few times but what i am facing now i had never faced before i had not investigated the code much but i just wanted to know that if some one knows off hand why the code "seq.open" and "seq.close" oepning a file physically.

Any way thanks for your fed backs!

As requested by other members - kindly post the code , that helps to debug.
else it would only be a guess work.

Hi friends,

Thansk for your time in but i had found the problem and fixed it.
It was an interesting one.
What was actually happening that while processing a session it used to print a report and at the same time create a log file on backend.
But in some scenario the log file was overwriting the file created by baan for printing finally either on Dispaly report or whatever the Device was selected by the user.

So actually it was the report getting printed i mean Dispalyed but with all the data written in Log file and not the Data for which it was meant.Actuall the client had given a snap sghot of the report it used to get soem time.
But we were nto able to reproduce it but finally some how hwen reproduced the error we found that the report is getting printed is correct one i mean in the report header the report code was the correct one but it printed the complete log file .