Doesn't \ in a list box or cbo disable the item?
Laurie
On 10 June 2014 23:50, mbsoftwaresoluti...@mbsoftwaresolutions.com wrote:
Found that the leading \0 was the cause/reason-to-blame for the cbo's
misbehavior. Retooled the CreateKey method by adding this before the
return:
IF
Hi Mike,
You also have at least 1 character that could cause problems with
different codepages / character encodings.
I'm not sure it's wise to use generate keys like this (though I
understand the reason).
Wouldn't it be safer to use a Guid (if your database supports it) or a
base-64 encoded
Hi Paul,
I had it initially set to use option level 0 (ansi human readable--38
wide), but changed the framework to use the 16-wide key instead to be
more compact. In hindsight, I'm wondering if the char(38) would be less
problematic should users outside the USA use it. What do you think???
Yes but in this case it wasn't disabling the value; it wasn't showing it
at all for some reason. Here's how I populate the cbo in the Init
event:
this.Clear
SELECT curJobTypes
SCAN
this.AddItem(ALLTRIM(curJobTypes.cJobType))
this.AddListItem(curJobTypes.cID,this.NewItemId,2)
...@leafe.com] On Behalf Of
mbsoftwaresoluti...@mbsoftwaresolutions.com
Sent: Wednesday, June 11, 2014 10:41 AM
To: profoxt...@leafe.com
Subject: Re: Interesting GOTCHA from 16-byte binary key
Yes but in this case it wasn't disabling the value; it wasn't showing it at all
for some reason. Here's
Of
mbsoftwaresoluti...@mbsoftwaresolutions.com
Sent: Wednesday, June 11, 2014 10:41 AM
To: profoxt...@leafe.com
Subject: Re: Interesting GOTCHA from 16-byte binary key
Yes but in this case it wasn't disabling the value; it wasn't showing
it at all for some reason. Here's how I populate the cbo in the Init
event
11, 2014 11:06 AM
To: profoxt...@leafe.com
Subject: RE: Interesting GOTCHA from 16-byte binary key
Good point. I've changed that LEFT(lcKey,1) to \ $ lcKey:
IF '\' $ lcKey THEN try again..don't like those as it caused
issue with cboJobType
lcKey
...@mbsoftwaresolutions.com
Sent: Wednesday, June 11, 2014 11:06 AM
To: profoxt...@leafe.com
Subject: RE: Interesting GOTCHA from 16-byte binary key
Good point. I've changed that LEFT(lcKey,1) to \ $ lcKey:
IF '\' $ lcKey THEN try again..don't like those as it caused
issue
... ;-)
--
rk
-Original Message-
From: ProfoxTech [mailto:profoxtech-boun...@leafe.com] On Behalf Of
mbsoftwaresoluti...@mbsoftwaresolutions.com
Sent: Wednesday, June 11, 2014 11:12 AM
To: profoxt...@leafe.com
Subject: RE: Interesting GOTCHA from 16-byte binary key
They're not displayed
To: profoxt...@leafe.com
Subject: RE: Interesting GOTCHA from 16-byte binary key
They're not displayed...they're all internal. What gave you that
impression? No, the 'dirty' feeling came from large field sizes for
keys. I didn't want the tree to be bloated. I liked the idea of the
smallest sized
Subject: RE: Interesting GOTCHA from 16-byte binary key
LOL...so back to the remaining question: do you think that non-USA users might
encounter issues if I'm using the binary instead of the unicode or ansi human
readable options? Here they are again from VFP2C32's help:
* 0 = ansi
that be a
concern?
--
rk
-Original Message-
From: ProfoxTech [mailto:profoxtech-boun...@leafe.com] On Behalf Of
mbsoftwaresoluti...@mbsoftwaresolutions.com
Sent: Wednesday, June 11, 2014 11:42 AM
To: profoxt...@leafe.com
Subject: RE: Interesting GOTCHA from 16-byte binary key
LOL...so back
To: profoxt...@leafe.com
Subject: RE: Interesting GOTCHA from 16-byte binary key
Paul Hill had mentioned something about the Code Pages and/or encoding.
I figured that happens to data behind the scenes, not necessarily if an
end-user is touching it. ???
On 2014-06-11 11:47, Richard Kaye wrote
[mailto:profoxtech-boun...@leafe.com] On Behalf Of
mbsoftwaresoluti...@mbsoftwaresolutions.com
Sent: Wednesday, June 11, 2014 11:59 AM
To: profoxt...@leafe.com
Subject: RE: Interesting GOTCHA from 16-byte binary key
Paul Hill had mentioned something about the Code Pages and/or encoding.
I figured that happens
On Wed, Jun 11, 2014 at 11:55 AM,
mbsoftwaresoluti...@mbsoftwaresolutions.com wrote:
If I make an app that works great here in the USA, what worries do I have
(with respect to how data is stored) if it goes overseas? Must I use
unicode? I mean--using English machines as a
Subject: RE: Interesting GOTCHA from 16-byte binary key
LOL...so back to the remaining question: do you think that non-USA
users might encounter issues if I'm using the binary instead of the
unicode or ansi human readable options? Here they are again from
VFP2C32's help:
* 0
-
From: ProfoxTech [mailto:profoxtech-boun...@leafe.com] On Behalf Of
mbsoftwaresoluti...@mbsoftwaresolutions.com
Sent: Wednesday, June 11, 2014 11:59 AM
To: profoxt...@leafe.com
Subject: RE: Interesting GOTCHA from 16-byte binary key
Paul Hill had mentioned something about the Code Pages
No no, Steve...yeah, email addresses and phone numbers are different but
I'm asking about how data is STORED? I couldn't care if it's .com or
.com.uk or .com.stephen.
On 2014-06-11 13:00, Stephen Russell wrote:
On Wed, Jun 11, 2014 at 11:55 AM,
mbsoftwaresoluti...@mbsoftwaresolutions.com
On Wed, Jun 11, 2014 at 12:39 PM,
mbsoftwaresoluti...@mbsoftwaresolutions.com wrote:
No no, Steve...yeah, email addresses and phone numbers are different but
I'm asking about how data is STORED? I couldn't care if it's .com or .
com.uk or .com.stephen.
-
Data is simple.
:59 AM
To: profoxt...@leafe.com
Subject: RE: Interesting GOTCHA from 16-byte binary key
Paul Hill had mentioned something about the Code Pages and/or
encoding.
I figured that happens to data behind the scenes, not necessarily if
an end-user is touching it. ???
On 2014-06-11 11:47, Richard Kaye
Of
mbsoftwaresoluti...@mbsoftwaresolutions.com
Sent: Wednesday, June 11, 2014 11:42 AM
To: profoxt...@leafe.com
Subject: RE: Interesting GOTCHA from 16-byte binary key
LOL...so back to the remaining question: do you think that non-USA
users might encounter issues if I'm using the binary instead
Sent: Wednesday, June 11, 2014 11:59 AM
To: profoxt...@leafe.com
Subject: RE: Interesting GOTCHA from 16-byte binary key
Paul Hill had mentioned something about the Code Pages and/or encoding.
I figured that happens to data behind the scenes, not necessarily if
an end-user is touching
On 2014-06-11 16:55, Stephen Russell wrote:
On Wed, Jun 11, 2014 at 3:36 PM,
mbsoftwaresoluti...@mbsoftwaresolutions.com wrote:
I'm not using Foxpro DBFs; I'm using MariaDB (MySQL) on the backend,
so I
guess no worries with that! ???
---
You need to identify the collation
On 2014-06-10 16:15, mbsoftwaresoluti...@mbsoftwaresolutions.com wrote:
I had a record where the primary key was '\0|±ß pM•wÑ©9†‚' (without
the beginning/ending quotes) and the cbo to which it was tied didn't
like it. I'm not sure if it was the leading \0 or the , near the end.
Thoughts?
Found that the leading \0 was the cause/reason-to-blame for the cbo's
misbehavior. Retooled the CreateKey method by adding this before the
return:
IF LEFT(lcKey,1) = '\' THEN try again..don't like those as it caused
issue with cboJobType
lcKey = this.CreateKey(tiLevel)
ENDIF
On
25 matches
Mail list logo
