First of all, thank you for your good product.
I have test HXTT Excel for interfacing my program and excel file.
after I insert or update some query, I catch some confused case.
my program ends normally, but when I click excel which shoud be modified, I get the message - "Excel File is Locking" - in this condition, I totally cannot see the contents of excel file. after some other second, it works but it is still LOCKED and I can only see the contents in read-only mode.
after killing my program, all things go well.
My question is
1. Does end of my program mean the complete of insertin or update job?
2. Can I release excel file without killing my program?
Thanks in advance.
>1. Does end of my program mean the complete of insertin or update job?
No. java.sql.Connection.close() if that .xls is using in jdbc url.
>2. Can I release excel file without killing my program?
Please use delayedClose=0 connection property.
delayedClose Indicates the delayed seconds for close transaction. That option is used to avoid frequent close/open table operations for following sqls. You can use 0~120 seconds. Default: 3. null
Thank you for your quick response.
I describe my program with some more detail.
My program is kind of demon. it work always and catch the request and do some database related job like insertion or update. database is, of course, xls file.
as the request is not so frequent, i do not use connection pool - this means I make connection when i get request and close connection when the job ends.
My first question is - in above environment - just after treating one request, the excel file seems to be locked - even I cannot open with read-only mode. after several times, there is backup file of excel file and I can open the xls file with read-only mode. I can open this file only after killing my demon program.
What I want to know is - in first, if ending database job needs several second after ending of request in my program, can i get the time when the database job is completed.
in second, what is problem for second case.. locked and needs killing my program.
I guess it is so weird case for you. I apologize my poor description. actually, I cannot supply my program as it is the part of some other system.
Can you guess what is the reason of my problems?
Thank you in advance.
>Can you guess what is the reason of my problems?
Please use delayedClose=0 connection property in jdbc url or code, then your issus will disappear.
delayedClose: Indicates the delayed seconds for close transaction. That option is used to avoid frequent close/open table operations for following sqls. You can use 0~120 seconds. Default: 3. null