The bigger problem is that I am getting to a point where I need this to
work or fork
out some money for a commercial one. I would prefer to use the Open Source
version and contribute as a tester. Once I go to a commercial one, it
doesn't
make much sense for us to test the Open Source driver.
I understand that this is all voluntary, but if there is any way you can
fix this
problem sooner, I would be very great full. I will also continue to
test the
driver extensively.
Paul Reeves wrote:
> Thomas Miller wrote:
>
>> In Crystal, all the numbers decimal places are out of place
>>
>> 0.53 shows up as 530000.
>>
>> With out this fix, there really isn't anything we can do testing
>> wise. Unfortunately I don't
>> know ODBC or C/C++ and can't give much help on the programming issue.
>>
>> Tell me if this makes sense.
>>
>
> Yep - this makes sense.
>
> The reason I haven't put the snapshot out earlier is because I
> discovered that the driver seems to mangle the datatypes during the
> metadata querying phase. This means that applications that do metadata
> lookups (ie the clever ones like Crystal and Access) get one thing and
> think it is something else. Or, they just ignore the bad data completely.
>
> I discovered this because I wanted to get to the bottom of the whole
> issue of why the driver doesn't work properly with Access.
>
> It appears to be a problem in the original release of the driver and
> not one that has crept in with recent enhancements. I didn't have the
> time to verify this before today, hence the delay.
>
> I'd like to get this fixed, but I wont have a chance to take a more
> serious look at it until next month.
>
> This only affects applications that rely on metadata querying. With
> pure SQL statements they are executed and data is retrieved correctly.
> Not much consolation if you are using Crystal or Access.
>
>
> Paul
--
Thomas Miller
Delphi Client/Server Certified Developer
BSS Accounting & Distribution Software
BSS Enterprise Accounting FrameWork
http://www.bss-software.com
|
