[AccessD] SQL Formatter (Was How To Display an Image from a Pervasive Database table Via Access 2007)

Jim Lawrence accessd at shaw.ca
Wed May 13 01:59:32 CDT 2015


I really like that online editor.

Jim

----- Original Message -----
From: "Bill Benson" <bensonforums at gmail.com>
To: "Access Developers discussion and problem solving" <accessd at databaseadvisors.com>
Sent: Tuesday, May 12, 2015 11:44:29 PM
Subject: Re: [AccessD] SQL Formatter (Was How To Display an Image from a Pervasive Database table Via Access 2007)

What part?
On May 12, 2015 1:34 PM, "Jim Lawrence" <accessd at shaw.ca> wrote:

> Hi Jurgen
>
> Is that ever cool. :-)
>
> Jim
>
> ----- Original Message -----
> From: "Jurgen Welz" <jwelz at hotmail.com>
> To: "Access Developers discussion and problem solving" <
> accessd at databaseadvisors.com>
> Sent: Monday, May 11, 2015 1:58:41 PM
> Subject: [AccessD] SQL Formatter (Was How To Display an Image from a
> Pervasive Database table Via Access 2007)
>
> I use http://poorsql.com/
> It does a great job of parsing the text into something much more
> comprehensible.
>
> I've been using Pervasive data since Sage bought out Precision Estimating
> (Timberline).  Sage's most recent foray into SQL server with their
> construction estimating product has us running two systems; Pervasive for
> the estimators and SQL Server for the project managers.  Their conversion
> to SQL Server was a total flop.  The whole system started out as text file
> fields limited to 50 characters concatenated a fixed number of times to a
> maximum field length.  This rule was simply carried over to the Pervasive
> and then SQL Server versions.  The result is unweildy in production.
>
> Pervasive itself was pretty slick and pulled data out of data stored in
> the file system.  There was a root file with metadata about the data files,
> a sub folder named 'PVData' and roughly 60 files beneath that approximately
> mapping to a table each.  The fun was copying estimate files and renaming
> the estimate without renaming the PVData folders to match.  It was not
> possible to mine data across multiple estimates without linking to multiple
> estimate backends (1 per estimate) or sequentially linking, extracting and
> compiling data in a aggregation database, but within a single estimate, it
> at least worked consistently and very quickly.
>
> In all our time with Pervasive, we've never had image data stored there so
> I can help on that issue.
>
> Ciao
> Jürgen Welz
> Edmonton, Alberta
>
> > Date: Mon, 4 May 2015 17:59:08 -0400
> > From: bensonforums at gmail.com
> > To: accessd at databaseadvisors.com
> > Subject: Re: [AccessD] How To Display an Image from a Pervasive Database
> table Via Access 2007
> >
> > Someone showed me an SQL editor that they pasted code into and it showed
> up
> > much better than in the Access SQL window. I wish I knew what that was, I
> > am sure it was a common editor many people use. Doesn't prevent Access
> from
> > messing with it afterward of course.
> >
> > On Mon, May 4, 2015 at 7:33 AM, Jim Lawrence <accessd at shaw.ca> wrote:
> >
> > > Ouch.
> > >
> > > Jim
>
> --
> 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
>
-- 
AccessD mailing list
AccessD at databaseadvisors.com
http://databaseadvisors.com/mailman/listinfo/accessd
Website: http://www.databaseadvisors.com



More information about the AccessD mailing list