I disagree that you are the only person who understands POI. I've written at least 2 implementations of structured storage, both some time ago and before POI. My knowledge of OLE structured storage is quite extensive, having worked on lots of bespoke client projects, and in data recovery (where you need an espcially detailed imeplemtatation, beacuse you often have POIFS-type files without complete information). Ive been working with POI recently, mostly for testing, and can say that I have a pretty good understanding of how it works, and whats it's probablems are (mostly memory issues).
Of course, I agree that if you want to be paid, you should. But I was only saying that *I* do not mind helping out with this knowledge for free. If poeple want to ask questions about how POIFS works (classes, implemenation, etc). I will be happy to answer for free, and in detail. -- Kais -----Original Message----- From: Andrew C. Oliver [mailto:[EMAIL PROTECTED] Sent: 26 February 2004 01:47 To: POI Users List Subject: Re: Problem generating a large file when following thePOIFSstandard You do realize I'm probably the only one left that understands how POIFS itself works. POI isn't merely a documentation project, it exists to provide free ports of the file format. If you worked on another related open source project I'd help you for free (collaborate) but otherwise, I'm certainly not willing to help you create proprietary forks of POI for free. -Andy > From: "Kais Dukes" <[EMAIL PROTECTED]> > Reply-To: "POI Users List" <[EMAIL PROTECTED]> > Date: Wed, 25 Feb 2004 22:49:16 -0000 > To: "POI Users List" <[EMAIL PROTECTED]> > Subject: RE: Problem generating a large file when following the POIFSstandard > > Dear Andrew, > > The code itself is only one part of the project. Perhaps even more valuable > than actual code is the documentation, and knowledge that poeple in this > group have. Its important to discuss the actual standards themselves. The > fact that Microsoft dont discuss these things, or make them public is > EXACTLY the reason why this project is so valuable. Perhaps we shouldn't be > so quick to turn away people asking questions about how POIFS persistance > works. Answering these questions will help people understand the code, and > find bugs, etc. > > The service is not free? Perhaps your time is not free, but if people are > asking questions about how POIFS works, Im happy to provide a free service, > wherever I can help. The quesiton was not C++ specific, it was merely about > the POIFS standard, so I think it's perfectly acceptable. > > I dont think you should have to donate code in order to get an answer about > how existing code works, even if you are deriving something from it, > especially under an Apache license. > > -- Kais > > -----Original Message----- > From: Andrew C. Oliver [mailto:[EMAIL PROTECTED] > Sent: 25 February 2004 22:40 > To: POI Users List > Subject: Re: Problem generating a large file when following the > POIFSstandard > > > Unless you plan to donate the C++ code to the project, I'm not sure this is > the appropriate place to ask your question. The source is open and free, > the service (like helping you work on a proprietary language fork of POI) > isn't. > -- > Andrew C. Oliver > http://www.superlinksoftware.com/poi.jsp > Custom enhancements and Commercial Implementation for Jakarta POI > > http://jakarta.apache.org/poi > For Java and Excel, Got POI? > > The views expressed in this email are those of the author and are almost > definitely not shared by the Apache Software Foundation, its board or its > general membership. In fact they probably most definitively disagree with > everything espoused in the above email. > >> From: "Brandon Belvin" <[EMAIL PROTECTED]> >> Organization: Information Systems Support, Inc. >> Reply-To: "POI Users List" <[EMAIL PROTECTED]> >> Date: Wed, 25 Feb 2004 16:04:00 -0600 >> To: "POI User Mailing List" <[EMAIL PROTECTED]> >> Subject: Problem generating a large file when following the POIFS standard >> >> As an add-on to an existing database front-end application, we have > allowed >> the user to export their report's data to Excel. Following POIFS' >> standards, we used C++ to write the Excel file. Upon testing, we > discovered >> our code works perfectly for files under 6.8 MB. For files larger than > 6.8 >> MB, it is necessary to use an XBAT. Excel will no longer open the file. >> The error message states the file is not repairable and cannot extract > data >> from the file. >> >> We adapted the code to calculate the number of XBATs needed and made >> appropriate changes to the self-description in the BATs. I've even gone > so >> far as to compare our generated file in HEX to an Excel XP file. > Everything >> looks the same for same-size files with the exception that we do not >> compress our string table. >> >> At this point, OpenOffice will successfully open the file but Excel will >> not. If we save the OpenOffice file as an Excel file, it does open >> properly. Since we cannot ask our customers to do this, this is not an >> viable solution. >> >> What potential pitfalls might we have fallen into? I'm thinking the > problem >> is related to our implementation of the XBAT, but I'm not sure since it >> looks the same as an Excel XP file. I'd be more than willing to provide a >> generated file to anyone who is able to help. Thanks in advance. >> >> Brandon Belvin >> Information Systems Support, Inc. >> >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: [EMAIL PROTECTED] >> For additional commands, e-mail: [EMAIL PROTECTED] >> > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
