[AccessD] Delimiter Value (was: Automatic Update Function)

[Jim Dettman]

I actually used :: in one situation where it worked pretty darn well.

I got tired of adding reference data to a database, so I took the big
shortcut of dumping entity value pairs in a memo field:

CDD::<<entity tag>>::<value>

('CDD' being "Customer Defined Data").  Never had a problem yet 

Not sure why I didn't think of using || though when I have used the pipe as
a single delimiter.

Jim.

-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of David McAfee
Sent: Tuesday, March 03, 2015 01:34 PM
To: Access Developers discussion and problem solving
Subject: Re: [AccessD] Delimiter Value (was: Automatic Update Function)

Hi my name is David and I'm also a Pipe delimeter ;)

I do like Arthur's idea of a double limiter like ||

D

On Tue, Mar 3, 2015 at 8:06 AM, Gustav Brock <gustav at cactus.dk> wrote:

> Hi Tina
>
> That character could be: ¤
> I've seen on every keyboard but never seen it used for anything.
>
> However, I've never had issues with the "|" pipe sign, so why make things
> more strange than necessary.
>
> /gustav
>
> -----Oprindelig meddelelse-----
> Fra: accessd-bounces at databaseadvisors.com [mailto:
> accessd-bounces at databaseadvisors.com] På vegne af Tina Norris Fields
> Sendt: 3. marts 2015 17:02
> Til: Access Developers discussion and problem solving
> Emne: Re: [AccessD] Delimiter Value (was: Automatic Update Function)
>
> This is an intriguing part of the discussion.  One perspective is to find
> a symbol that will not accidentally be typed because it's not on a
standard
> keyboard.  The other perspective is to find a symbol that can easily be
> used (because it is on a standard keyboard), but is not commonly used for
> most typing and coding.  Fascinating.  I like the pipe symbol because it
> fits with the second perspective.  I would like an
> ALT+ASCII code symbol that is easy to remember and doesn't appear on a
> standard keyboard, too, because it reduces the threat of accidental
> typing.  Hmmm - pondering.
> TNF
>
> Tina Norris Fields
> tinanfields-at-torchlake-dot-com
> 231-322-2787
>
> On 3/3/2015 8:13 AM, Jim Dettman wrote:
> >
> >   I'm not sure if it's as true today as it once was, but using
> > anything beyond 127 was iffy.
> >
> >   The extended characters have no set definition unlike those below
> > 128.  So while that may not exist as a character on a US keyboard, it
> > may exist on others because it might not be a cent symbol.
> >
> >   I use the vertical pipe as well because to my knowledge, there's no
> > place where one would use it outside of computer commands and it is
> > easy to read because the character is thin.
> >
> > Jim.
> >
> > -----Original Message-----
> > From: accessd-bounces at databaseadvisors.com
> > [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Dan Waters
> > Sent: Monday, March 02, 2015 08:59 PM
> > To: 'Access Developers discussion and problem solving'
> > Subject: Re: [AccessD] Delimiter Value (was: Automatic Update
> > Function)
> >
> > Hi John,
> >
> > A pretty safe delimiter is a ¢ symbol (cent symbol).  To use it,
> > you'll have to find it somewhere and copy it into your code.  Or, you
> > can could also use Chr(162).
> >
> > I don't think a cent symbol is on any US electronic keyboards, and
> > certainly not on any others.
> >
> > I found a good list of Chr values at
> > http://www.gtwiki.org/mwiki/?title=VB_Chr_Values.
> >
> > Dan
> >
> > -----Original Message-----
> > From: accessd-bounces at databaseadvisors.com
> > [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of John W.
> > Colby
> > Sent: Monday, March 02, 2015 15:32 PM
> > To: Access Developers discussion and problem solving
> > Subject: Re: [AccessD] Automatic Update Function
> >
> > Of course it was simple.  However if you look at SQL Server export for
> > example, by default if you tell it to use quotes, it quotes EVERY FIELD.
> >
> > So if you are getting data from the wild, look out.  If you are doing
> > the export yourself, and then the import yourself, it is really fairly
> > easy, you control both ends.
> >
> > As I mentioned I like pipe delimited because (in MY data) pipes are
> > unheard of, so using that as a delimiter is pretty safe.  My data is
> > name / address from the wild, so tabs are encountered occasionally. I
> > have never actually seen a pipe coming in from raw data, though of
> > course it is a key on the keyboard and someone could accidentally hit
it.
> >
> > John W. Colby
>
> --
> AccessD mailing list
> AccessD at databaseadvisors.com
> http://databaseadvisors.com/mailman/listinfo/accessd
> Website: http://www.databaseadvisors.com
>
-- 
AccessD mailing list
AccessD at databaseadvisors.com
http://databaseadvisors.com/mailman/listinfo/accessd
Website: http://www.databaseadvisors.com