| Author |
 Topic  |
|
|
d.kirchner
Germany
3 Posts |
 Posted - 10 Sep 2013 : 13:10:16
|
Hi,
in my last tests with Pulsonix 7.6 Build 5223 I could not search values like e.g. in OrCAD CIS.
I tried to find a part with 10000 Ohms and put into the search criteria "VALUE = 10000", no part was found.
With "VALUE = 10k" I've got a Part.
When using the operator "between" with 1K and 2K I'm getting following values back: 1M, 2.2, 2.2K, 2.7, 2.7K, 22, 22K and so on...
I haven't found anything in the release notes for Pulsonix 8.0 about this error
Could anyone tell me something about this behaviour?
Thx
David Kirchner |
|
|
bkamen
USA
49 Posts |
Posted - 10 Sep 2013 : 23:19:56
|
quote:
Originally posted by d.kirchner
Hi,
in my last tests with Pulsonix 7.6 Build 5223 I could not search values like e.g. in OrCAD CIS.
I tried to find a part with 10000 Ohms and put into the search criteria "VALUE = 10000", no part was found.
With "VALUE = 10k" I've got a Part.
When using the operator "between" with 1K and 2K I'm getting following values back: 1M, 2.2, 2.2K, 2.7, 2.7K, 22, 22K and so on...
I haven't found anything in the release notes for Pulsonix 8.0 about this error
Could anyone tell me something about this behaviour?
If I could ask first:
Where are you putting in the "VALUE = 10k"?
Is this in the dialog box that appears when adding a part from your libraries?
And this is going in the "filter" field?
Yes?
And just FYI, I'm not on PSX v8 yet.
-------------------------------------------
bkamen@benjammin.net
http://www.benjammin.net |
 |
|
|
d.kirchner
Germany
3 Posts |
Posted - 11 Sep 2013 : 10:24:39
|
Hi bkamen,
for a better understanding I took some screenshots.
You'll find them here: (upload-function in this forum doesn't work).
https://skydrive.live.com/redir?resid=D98EF9F122F76761!147
1) Test with "VALUE = 10000"
2) Test with "VALUE = 10K"
3) Test with "VALUE between 1K and 2K"
David |
Edited by - d.kirchner on 11 Sep 2013 12:11:30 |
|
|
|
bkamen
USA
49 Posts |
Posted - 11 Sep 2013 : 14:27:34
|
Ahhh,
I think I see.
ok, first off, it looks like you're using the database connection "part" of pulsonix which I don't. (I use the native parts stuff built into PSX)
With that, just from looking at your screens, the comment that comes to mind (as an ex-IT guy, but still do it for fun) is that the VALUE field is being stored as a TEXT string, not a numeric on.
So a search for "10000" will fail because the field is "10K".
Just as "10,000" would fail because there's no comma in the field on the server.
Of course, PSX Support can correct me if I'm wrong, but I believe the answer to your problem is to think that you are doing a text string match not a numeric match.
If you wanted to be able to search for 10000 or 10K you'd need a VALUE2 field set with "10000" since VALUE is already set to "10K"
Make sense?
-Ben
-------------------------------------------
bkamen@benjammin.net
http://www.benjammin.net |
Edited by - bkamen on 11 Sep 2013 14:29:11 |
|
|
|
d.kirchner
Germany
3 Posts |
Posted - 12 Sep 2013 : 08:48:08
|
Hi Ben
quote:
Originally posted by bkamen
With that, just from looking at your screens, the comment that comes to mind (as an ex-IT guy, but still do it for fun) is that the VALUE field is being stored as a TEXT string, not a numeric on.
You are right, the VALUE field is from typ TEXT.
Database is in form of a MS Access database.
But when I remember correctly, the OrCAD CIS-database (was a MySQL-DB) has also a TEXT field but OrCAD CIS interpreted it as a number and also understand metric prefix like k,M,G,m,ยต,n,p.
Maybe PSX Support has any idea.
David
|
|
|
|
psxforum
United Kingdom
66 Posts |
Posted - 17 Sep 2013 : 15:39:16
|
What you have worked out is just about right, the field being Text is searched purely as Text and has no special meaning. When we post an SQL query through the ODBC connection, we can only construct that query using things that are valid in such a query. Sadly this does not include things like SELECT * FROM CAPS WHERE 'VALUE' < 100K
However, we do recognise that this is an issue to some PDC users, so we are looking at what can be done about this without the user having to construct an extra column in their table/view to present the value in a unified form (for example presenting 100K as 100000). |
|
|
| |
Topic |
|
|
|
