Issue 76810 - Bug in put command (for binary access)
Summary: Bug in put command (for binary access)
Status: CLOSED FIXED
Alias: None
Product: App Dev
Classification: Unclassified
Component: scripting (show other issues)
Version: 3.3.0 or older (OOo)
Hardware: All All
: P3 Trivial
Target Milestone: 4.2.0
Assignee: ab
QA Contact:
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-04-30 15:33 UTC by szodrow
Modified: 2016-07-21 18:34 UTC (History)
2 users (show)

See Also:
Issue Type: DEFECT
Latest Confirmation in: ---
Developer Difficulty: ---

Attachments
Calc file with macro that shows the problem (10.62 KB, text/plain)
2007-04-30 15:36 UTC, szodrow 		no flags Details
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this issue.
Description szodrow 2007-04-30 15:33:42 UTC 
I want to write a csv file. The write command encloses everything with double
quotes, so I use binary mode and apply newline characters by hand. I use the
following put syntax:

put iFileNo, , sString

This works fine for about 1000 characters. Then everything is missing except the
last record. I can use a workaround with the following syntax:

put iFileNo, posCounterOnMyOwn, sString

and track the write position on my own. This is not nice and should be fixed
together with (my) Issue 74375 read file with fix...

:-)
Comment 1 szodrow 2007-04-30 15:36:10 UTC 
Created attachment 44778 [details]
Calc file with macro that shows the problem
Comment 2 noel.power 2007-05-01 18:45:09 UTC 
->ab
Comment 3 ab 2007-05-08 07:40:01 UTC 
Started, OOo 2.x
Comment 4 Mathias_Bauer 2007-12-04 14:57:30 UTC 
basic and scripting issues now should be assigned to component "scripting"
Comment 5 Martin Hollmichel 2007-12-07 12:13:30 UTC 
set target to 3.x according to http://wiki.services.openoffice.org/wiki/Target_3x
Comment 6 szodrow 2009-12-23 16:59:26 UTC 
szodrow->ab: Can be closed
Comment 7 damjan 2016-07-21 13:29:33 UTC 
Can't reproduce any more, on Windows 8 or 32 bit Ubuntu Linux 14.04. Probably fixed by the new(ish) _USE_UNO file I/O that we use now instead. Resolving fixed.