| View previous topic :: View next topic |
| Author |
Message |
Qalam
Blue Pill
Joined: Apr 19, 2010
Posts: 3
|
 Posted: Mon Apr 19, 2010 6:49 am Post subject: ODB forms import error from ODS spreadsheet |
|
Since updating to 3.0.2, I have an import problem in ODB forms.
The form imports field data from an ODS spreadsheet. The spreadsheet is a timesheet that contains the hours worked each day (columns) in a given week (rows) and calulates the total hours for the week.
The form simply shows the data for a particular week (i.e., imports several fields from a given row in the spreadsheet).
Randomly, one or another of the form fields displays a value that is less than the value in the spreadsheet for the day in question. Usually the decimal portion of the value has been dropped and replaced with 00.
I export the form to a pdf and email it to another person. I have attached a sample pdf showing the value display error with added comments. This worked fine for 62 weeks, until I updated to 3.0.2 about a month ago. |
|
| Back to top |
|
 |
pluby
The Architect
Joined: Jun 16, 2003
Posts: 11949
|
| Posted: Mon Apr 19, 2010 7:32 am Post subject: Re: ODB forms import error from ODS spreadsheet |
|
| Qalam wrote: | | Randomly, one or another of the form fields displays a value that is less than the value in the spreadsheet for the day in question. Usually the decimal portion of the value has been dropped and replaced with 00. |
Is there any way that you can share a sample .ods and .odb files that we can use to reproduce the problem that you see? If you can share the files, can you attach them using the steps in this forum post.
One other question: does this problem occur in NeoOffice 3.1.1 Beta? We released NeoOffice 3.1.1 Beta earlier this month and that version is based on a OpenOffice.org 3.1.1 whereas NeoOffice 3.0.2 is based the much older OpenOffice.org 3.0.1 code.
If you don't have NeoOffice 3.1.1 Beta installed, can you download it from here, install it, and tell us if this same problem occurs?
Note: if you want to keep NeoOffice 3.0.2 installed on your machine, before you install NeoOffice 3.1.1 Beta go to the /Applications folder in the Finder, click on the NeoOffice icon's name, press the Return key, and change the name. For example, I changed mine to NeoOffice-3.0.2. This will ensure that the NeoOffice 3.1.1 Beta installer will not overwrite your NeoOffice 3.0.2 installation.
Patrick |
|
| Back to top |
|
|
Qalam
Blue Pill
Joined: Apr 19, 2010
Posts: 3
|
| Posted: Mon Apr 19, 2010 10:31 am Post subject: |
|
After checking, it appears that the problem has been around since November 2009, that is, just after I upgraded to NO 2.2.6 (released on Oct. 29, 2009).
The obd form display problem only appears in two fields (lundi and samedi). It does not appear if I generate an odb report for all the rows in my spreadsheet.
I have attacked a zip file of my odb and ods files. |
|
| Back to top |
|
|
pluby
The Architect
Joined: Jun 16, 2003
Posts: 11949
|
| Posted: Mon Apr 19, 2010 11:32 am Post subject: |
|
Thank you for the .zip file. I can reproduce this problem when in the lundi and samedi columns when those columns have "vacation" as the value. In those cases, the form shows "0,00".
I will investigate and see if there is anything I can do to fix this problem. I will post again when I have some news to report.
Patrick |
|
| Back to top |
|
|
pluby
The Architect
Joined: Jun 16, 2003
Posts: 11949
|
| Posted: Tue Apr 20, 2010 5:15 am Post subject: |
|
I found the cause of the problem and it appears to be simple to correct. Can you try the following steps?:
1. Open the .odb file and Control-click on the form. In the popup menu that appears, select the Edit menu.
2. In the form design window that appears, Control-click on the "lundi" text box and in the popup menu that appears, select the Group :: Edit Group menu. Then double-click on the text box until the "Properties: Formatted Field" window appears.
3. In the "Properties: Formatted Field" window, click on the General tab and scroll down to the Formatting field. Delete any text in that field as it is that text that is causing the problem.
4. Repeat steps 2 and 3 for the "samedi" text box.
Do the above steps fix the problem for you?
Patrick |
|
| Back to top |
|
|
Qalam
Blue Pill
Joined: Apr 19, 2010
Posts: 3
|
| Posted: Wed Apr 21, 2010 4:41 pm Post subject: |
|
Yes, that fixed the problem. I'm not sure when or why I changed the formatting from "standard number" (Canadian French) to the value that was in the two form fields. I don't use the database function very often, so this has helped me better understand what I'm doing. Thanks. Live long and prosper!  |
|
| Back to top |
|
|
pluby
The Architect
Joined: Jun 16, 2003
Posts: 11949
|
| Posted: Wed Apr 21, 2010 5:03 pm Post subject: |
|
| Qalam wrote: | | Yes, that fixed the problem. I'm not sure when or why I changed the formatting from "standard number" (Canadian French) to the value that was in the two form fields. I don't use the database function very often, so this has helped me better understand what I'm doing. Thanks. Live long and prosper! |
I suspect that Base created these formatting settings automatically when NeoOffice 3.0.2 loaded your .ods file for the first time. I believe that NeoOffice 3.0.2 tries to guess the best format by scanning the first few rows of data in each column and NeoOffice's underlying OpenOffice.org code guessed badly.
Patrick |
|
| Back to top |
|
|
|
