Re: MariaDB limitation on memo fields -- caps out at 255

2019-02-27 Thread Eric Selje
Well it's happened again where I discover a blog post I made that helps me
towards a current problem. Looking here:

http://saltydogllc.com/on-vfp-and-mysql-connectionstrings/

Here are the options (at the time, I doubt they've changed):
2 = Return matched rows instead of affected rows
8 = Allow big result sets
16 = Don’t prompt when connecting
32 = Enable dynamic cursors
64 = Ignore schema in column specifications
128 = Disable driver-provided cursor support
256 = Don’t use setlocale()
512 = Pad CHAR to full length with space
1024 = Include table name in SQLDescribeCol()
2048 = Use compression
4096 = Ignore space after function names
8192 = Force use of named pipes
16384 = Treat BIGINT columns as INT columns
32768 = Disable catalog support
65536 = Read options from my.cnf
131072 = Enable safe options (see documentation)
262144 = Disable transaction support
524288 = Log queries to myodbc.sql
1048576 = Don’t cache results of forward-only cursors
2097152 = Force use of forward-only cursors
4194304 = Enable automatic reconnect
8388608 = Enable SQL_AUTO_IS_NULL
67108864 = Allow multiple statements
134217728 = Limit column size to signed 32-bit range
268435456 = Always handle binary function results as character data

Your value of 67174427 means:
67108864 = Allow multiple statements +
65536 = Read options from my.cnf +
16 = Don’t prompt when connecting +
8 = Allow big result sets +
2 = Return matched rows instead of affected rows +
1 (I don't know what this means)

Not sure what's in your *my.cnf* that might affect the results. Maybe throw
a 512 or 64 in there to see what happens?

Eric




On Wed, Feb 27, 2019 at 11:16 AM <
mbsoftwaresoluti...@mbsoftwaresolutions.com> wrote:

> I'd appreciate that, Eric.  I'm using 67174427.
>
>
> On 2019-02-25 14:42, Eric Selje wrote:
> > Yes I'd check your ConnectionString Options. Whil Hentzen's book about
> > devloping with Fox and MySQL (Maria) goes over all of those.  I can
> > check
> > it if you'd like.
> >
> > Eric
> >
> > On Mon, Feb 18, 2019 at 7:36 PM
> > 
> > wrote:
> >
> >> On 2019-02-18 18:07, Fred Taylor wrote:
> >> > Mike,
> >> >
> >> > Are you sure it's not a TINYTEXT field?  TINYTEXT is 0 to 255 chars.
> >> >
> >> > TEXT is 65,535
> >> >
> >> > And MEDIUMTEXT is 16,777,215.
> >> >
> >> > Fred
> >>
> >>
> >> I'll double-check but I'm thinking it's my connection string OPTIONS
> >> value.
> >>
[excessive quoting removed by server]

___
Post Messages to: ProFox@leafe.com
Subscription Maintenance: http://mail.leafe.com/mailman/listinfo/profox
OT-free version of this list: http://mail.leafe.com/mailman/listinfo/profoxtech
Searchable Archive: http://leafe.com/archives/search/profox
This message: 
http://leafe.com/archives/byMID/profox/CAAwxvU=mpy2dm8cfzzrfnebefsdyoq-+wr5xx98mjcszmeq...@mail.gmail.com
** All postings, unless explicitly stated otherwise, are the opinions of the 
author, and do not constitute legal or medical advice. This statement is added 
to the messages for those lawyers who are too stupid to see the obvious.

Re: Creating a copy of a database -- best practice?

2019-02-27 Thread Charlie-gm


Ok, I haven't done this in a while, but I think I have done this a few ways.

First, by "metadata" of the database, I assume you mean stored 
procedures, maybe table triggers, database comment field?


I'll also assume you are trying to run from within an .exe (so commands 
like COPY PROCEDURES TO...  and APPEND PROCEDURES FROM ... will not be 
available)


So...

1) if you know the "data model" of the dbc, you can open it like a table 
- then look for the metadata items you want (the stored procedure code, 
trigger code, etc). Do a SCATTER MEMO NAME ... Then open the other DBC 
as a table and do an APPEND FROM NAME ... After everything is copied 
that way I think you will want to do a PACK DATABASE or maybe VALIDATE 
DATABASE on the backup. I seem to recall doing that.


2) after you've copied all the tables, copy the "database files" with 
"COPY FILE  TO " - copy the dbc, dct, and dcx this way. 
Again a PACK or VALIDATE database may be needed afterwards. And of 
course, be careful with this, test it out, etc. But I definitely used 
this approach before.


3) if you are not worried about the tables being opened at the time of 
doing the backup, you could just do the "COPY FILE  TO " - 
that command allows paths in the from/to. Also, I think it allows 
wildcards, so you could do a complete copy in 1 command. Of course, the 
downside is the assumption of files being closed.


-HTH,
-Charlie


On 2/27/2019 12:22 PM, mbsoftwaresoluti...@mbsoftwaresolutions.com wrote:

I can easily do something like this:

CREATE DATABASE C:\Backup\MyDBC.dbc
OPEN DATABASE C:\Production\MyDBC.dbc
liNumTables = adbobjects(laTables,'TABLE')
for ii = 1 to liNumTables
  lcFile = forceext("C:\BACKUP\" + laTables[ii],'dbf')
  use laTables[ii]
  copy to (lcFile) database C:\Backup\MyDBC.dbc with cdx
  use
endfor


...and that would get me a copy of all of the tables with their 
indexes.  Great.  But what's the easiest way to get all of the DBC 
meta-data into that new Backup database copy?  I can't USE the 
MyDBC.dbc and do a COPY TO as that only makes the result a DBF and FPT.


Trying to think about a good disaster recovery plan (besides using 
CleverFox from Rick Schummer and Frank Perez...which is probably the 
best option!) for automating backups at the client who just got that 
ransomware virus.


tia,
--Mike


[excessive quoting removed by server]

___
Post Messages to: ProFox@leafe.com
Subscription Maintenance: http://mail.leafe.com/mailman/listinfo/profox
OT-free version of this list: http://mail.leafe.com/mailman/listinfo/profoxtech
Searchable Archive: http://leafe.com/archives/search/profox
This message: 
http://leafe.com/archives/byMID/profox/ff594e8b-a5da-3f8d-99f4-e48189979...@gmail.com
** All postings, unless explicitly stated otherwise, are the opinions of the 
author, and do not constitute legal or medical advice. This statement is added 
to the messages for those lawyers who are too stupid to see the obvious.

Re: false news....

2019-02-27 Thread mbsoftwaresolutions

On 2019-02-22 14:50, Kevin Cully wrote:
There are a ton of VFP developers and they've never reached out to 
their community to improve their skills and it shows in their code.



So true!  Together, we're better.  

___
Post Messages to: ProFox@leafe.com
Subscription Maintenance: http://mail.leafe.com/mailman/listinfo/profox
OT-free version of this list: http://mail.leafe.com/mailman/listinfo/profoxtech
Searchable Archive: http://leafe.com/archives/search/profox
This message: 
http://leafe.com/archives/byMID/profox/a3600e4a845aad4c00b719ad780af...@mbsoftwaresolutions.com
** All postings, unless explicitly stated otherwise, are the opinions of the 
author, and do not constitute legal or medical advice. This statement is added 
to the messages for those lawyers who are too stupid to see the obvious.


Re: MariaDB limitation on memo fields -- caps out at 255 (SOLVED)

2019-02-27 Thread mbsoftwaresolutions

On 2019-02-23 01:23, mbsoftwaresoluti...@mbsoftwaresolutions.com wrote:

On 2019-02-18 15:50, mbsoftwaresoluti...@mbsoftwaresolutions.com wrote:

My VFP9SP2 app connects to my web database with no issue.  My client
wanted to host the database on his network there so I installed
MariaDB there and everything seemed to fire up just fine.  HOWEVER,
there's a problem with the memo fields capping at length=255.  Given
that it works with a different (my web) MariaDB database, I'm sure
this is a configuration issue.  Question is: where do I find/set that?

His network OS is Windows 2016 Server.  My web database is using a
Linux OS iirc.

tia,
--Mike



Here's the weird fix:  instead of using a MEDIUMTEXT field, it worked
just fine when I changed it to TEXT fields.  Now MEDIUMTEXT is
supposed to handle LARGER #s of characters, but in this case, just
TEXT should suffice.

Still...wonder why the ODBC (originally 3.51, then I upgraded to the
latest 64-bit MariaDB driver) has a problem with MEDIUMTEXT on this
Windows 2016 Server?  My other database (where no issues at all)
operates on a Debian Linux OS.

Thoughts?



No takers on this one. Look at the solution above.  Thoughts on why TEXT 
worked and not MEDIUMTEXT (which is larger than TEXT iirc)?


tia,
--Mike

___
Post Messages to: ProFox@leafe.com
Subscription Maintenance: http://mail.leafe.com/mailman/listinfo/profox
OT-free version of this list: http://mail.leafe.com/mailman/listinfo/profoxtech
Searchable Archive: http://leafe.com/archives/search/profox
This message: 
http://leafe.com/archives/byMID/profox/f743075b64adf1083a3e34348960e...@mbsoftwaresolutions.com
** All postings, unless explicitly stated otherwise, are the opinions of the 
author, and do not constitute legal or medical advice. This statement is added 
to the messages for those lawyers who are too stupid to see the obvious.


RE: [NF] Registering DLL's

2019-02-27 Thread Tracy Pearson
I haven't tried that. If it comes up again. I'll see if we can try it.

-Original Message-
From: ProFox [mailto:profox-boun...@leafe.com] On Behalf Of Alan Bourke
Sent: Wednesday, February 27, 2019 8:58 AM
To: profoxt...@leafe.com
Subject: Re: [NF] Registering DLL's


On a problem machine, does running your installer with /LOG and then
examining the log when it fails give any clues ?

-- 
  Alan Bourke
  alanpbourke (at) fastmail (dot) fm

[excessive quoting removed by server]

___
Post Messages to: ProFox@leafe.com
Subscription Maintenance: http://mail.leafe.com/mailman/listinfo/profox
OT-free version of this list: http://mail.leafe.com/mailman/listinfo/profoxtech
Searchable Archive: http://leafe.com/archives/search/profox
This message: 
http://leafe.com/archives/byMID/profox/01d4cec0$ddeb8730$99c29590$@powerchurch.com
** All postings, unless explicitly stated otherwise, are the opinions of the 
author, and do not constitute legal or medical advice. This statement is added 
to the messages for those lawyers who are too stupid to see the obvious.


Creating a copy of a database -- best practice?

2019-02-27 Thread mbsoftwaresolutions

I can easily do something like this:

CREATE DATABASE C:\Backup\MyDBC.dbc
OPEN DATABASE C:\Production\MyDBC.dbc
liNumTables = adbobjects(laTables,'TABLE')
for ii = 1 to liNumTables
  lcFile = forceext("C:\BACKUP\" + laTables[ii],'dbf')
  use laTables[ii]
  copy to (lcFile) database C:\Backup\MyDBC.dbc with cdx
  use
endfor


...and that would get me a copy of all of the tables with their indexes. 
 Great.  But what's the easiest way to get all of the DBC meta-data into 
that new Backup database copy?  I can't USE the MyDBC.dbc and do a COPY 
TO as that only makes the result a DBF and FPT.


Trying to think about a good disaster recovery plan (besides using 
CleverFox from Rick Schummer and Frank Perez...which is probably the 
best option!) for automating backups at the client who just got that 
ransomware virus.


tia,
--Mike

___
Post Messages to: ProFox@leafe.com
Subscription Maintenance: http://mail.leafe.com/mailman/listinfo/profox
OT-free version of this list: http://mail.leafe.com/mailman/listinfo/profoxtech
Searchable Archive: http://leafe.com/archives/search/profox
This message: 
http://leafe.com/archives/byMID/profox/500593bf5f84e661f7648a5121a41...@mbsoftwaresolutions.com
** All postings, unless explicitly stated otherwise, are the opinions of the 
author, and do not constitute legal or medical advice. This statement is added 
to the messages for those lawyers who are too stupid to see the obvious.


Re: MariaDB limitation on memo fields -- caps out at 255

2019-02-27 Thread mbsoftwaresolutions

I'd appreciate that, Eric.  I'm using 67174427.


On 2019-02-25 14:42, Eric Selje wrote:

Yes I'd check your ConnectionString Options. Whil Hentzen's book about
devloping with Fox and MySQL (Maria) goes over all of those.  I can 
check

it if you'd like.

Eric

On Mon, Feb 18, 2019 at 7:36 PM 


wrote:


On 2019-02-18 18:07, Fred Taylor wrote:
> Mike,
>
> Are you sure it's not a TINYTEXT field?  TINYTEXT is 0 to 255 chars.
>
> TEXT is 65,535
>
> And MEDIUMTEXT is 16,777,215.
>
> Fred


I'll double-check but I'm thinking it's my connection string OPTIONS
value.


[excessive quoting removed by server]

___
Post Messages to: ProFox@leafe.com
Subscription Maintenance: http://mail.leafe.com/mailman/listinfo/profox
OT-free version of this list: http://mail.leafe.com/mailman/listinfo/profoxtech
Searchable Archive: http://leafe.com/archives/search/profox
This message: 
http://leafe.com/archives/byMID/profox/fbb6724da613f39736b11588b1c58...@mbsoftwaresolutions.com
** All postings, unless explicitly stated otherwise, are the opinions of the 
author, and do not constitute legal or medical advice. This statement is added 
to the messages for those lawyers who are too stupid to see the obvious.


Re: Webfaction question

2019-02-27 Thread Ed Leafe
On Feb 22, 2019, at 1:51 PM, Kevin Cully  wrote:
> 
> I've really liked working with DigitalOcean.  I know people combine the DO 
> Server with the NameCheap service for an entire solution.

Like me?

Every ProFox email goes through DO servers. Every ProFox archive search goes 
through DO servers. And I use NameCheap for my domains.

The technology side of DO is rock-solid, which I really like. But what I like 
even more is their “how-to” documentation. You can find a over 2000 (!) of them 
here: 

https://www.digitalocean.com/community/tutorials/


-- Ed Leafe






___
Post Messages to: ProFox@leafe.com
Subscription Maintenance: http://mail.leafe.com/mailman/listinfo/profox
OT-free version of this list: http://mail.leafe.com/mailman/listinfo/profoxtech
Searchable Archive: http://leafe.com/archives/search/profox
This message: 
http://leafe.com/archives/byMID/profox/c77d196f-fc5d-4421-ae4c-7b9711972...@leafe.com
** All postings, unless explicitly stated otherwise, are the opinions of the 
author, and do not constitute legal or medical advice. This statement is added 
to the messages for those lawyers who are too stupid to see the obvious.

Re: false news....

2019-02-27 Thread Kevin Cully
Forgive yourself and move on.  :D  We've all made bad design decisions 
at one point or another in the past.  The most important part is that 
you are active in a developer community and seek to do better.  I hope 
that I am a better developer today than I was yesterday.  There are a 
ton of VFP developers and they've never reached out to their community 
to improve their skills and it shows in their code.



On 2/22/19 12:57 PM, M Jarvis wrote:

On Fri, Feb 22, 2019 at 6:11 AM Kevin J Cully 
wrote:



I had a potential client where they based their primary keys based on
employee Social Security Numbers.  They didn't like it when I told them
that they'd need a complete rewrite. Notice this would have been the case
no matter what language/technology they were using.  It was just piss poor
design.



I must confess I did this once and used SSN's as a primary key. It is
my shame

I was told I had a year and a half to write a enterprise wide application
and out of the blue the reality was I had about 3 weeks, and failure would
have cost millions and millions... oh - and my job...

I was panicked and the first thing I thought to use was the SSN thinking
that certainly they wouldn't be changing so as a PK would be handy to use.
I went for it w/o thinking it through...

Granted, this was back in the day when the internet wasn't what we think of
today, but still - it was a really dumb dumb idea I always regretted...



___
Post Messages to: ProFox@leafe.com
Subscription Maintenance: http://mail.leafe.com/mailman/listinfo/profox
OT-free version of this list: http://mail.leafe.com/mailman/listinfo/profoxtech
Searchable Archive: http://leafe.com/archives/search/profox
This message: 
http://leafe.com/archives/byMID/profox/b7be1462-b482-6f69-309a-cccb6f4d7...@cully.biz
** All postings, unless explicitly stated otherwise, are the opinions of the 
author, and do not constitute legal or medical advice. This statement is added 
to the messages for those lawyers who are too stupid to see the obvious.

Re: Webfaction question

2019-02-27 Thread Kevin Cully
I've really liked working with DigitalOcean.  I know people combine the 
DO Server with the NameCheap service for an entire solution.


On 2/22/19 2:41 PM, Ken McGinnis wrote:
I started using webfaction many years ago because someone on this list 
mentioned it. I have been very happy. However, now Webfaction has been 
taken over by Godaddy and none of my old procedures work for some 
reason. Also, they are not very responsive to questions. For example: 
I have several web sites on Webfaction and have my DNS server 
(name.com) pointed to them and it works fine. However, I used to be 
able to 'hide' things in a sub folder of one of those web sites and 
allow anyone to see what was there (sometimes with a password). Now I 
can't do that using FileZilla client. I set the permissions to 777 and 
there is no access at all. The subfolder can't even be seen in a 
directory list. Anyone have the same experience?


What I really want to know is if anyone has had good experience with a 
cheap (Linux?) server where I can put my web sites. I don't need email 
or any else other than storage, about 150gb or more.



---
This email has been checked for viruses by Avast antivirus software.
https://www.avast.com/antivirus



[excessive quoting removed by server]

___
Post Messages to: ProFox@leafe.com
Subscription Maintenance: http://mail.leafe.com/mailman/listinfo/profox
OT-free version of this list: http://mail.leafe.com/mailman/listinfo/profoxtech
Searchable Archive: http://leafe.com/archives/search/profox
This message: 
http://leafe.com/archives/byMID/profox/5ee2d670-ba1f-7f32-f88d-39d60e2eb...@cully.biz
** All postings, unless explicitly stated otherwise, are the opinions of the 
author, and do not constitute legal or medical advice. This statement is added 
to the messages for those lawyers who are too stupid to see the obvious.

Re: [NF] Registering DLL's

2019-02-27 Thread Alan Bourke


On a problem machine, does running your installer with /LOG and then examining 
the log when it fails give any clues ?

-- 
  Alan Bourke
  alanpbourke (at) fastmail (dot) fm

___
Post Messages to: ProFox@leafe.com
Subscription Maintenance: http://mail.leafe.com/mailman/listinfo/profox
OT-free version of this list: http://mail.leafe.com/mailman/listinfo/profoxtech
Searchable Archive: http://leafe.com/archives/search/profox
This message: 
http://leafe.com/archives/byMID/profox/f2decced-c37a-4ba8-a535-49924600d...@www.fastmail.com
** All postings, unless explicitly stated otherwise, are the opinions of the 
author, and do not constitute legal or medical advice. This statement is added 
to the messages for those lawyers who are too stupid to see the obvious.