Re: UCLA & FoxPro...
Love is a Pretty strong word there Mike! Although - the people interviewing me might agree with you. I used to tell people - when they say they love some "thing" - that you can't love an inanimate object! Sure - I have Solid Long time exp. w/The Fox! Done a Ton of work w/The Fox. So - yeah, a job working w/The Fox - its comfortable coming back to that kind of Code base & Dev. environ.! -K- On 3/3/2019 6:47 PM, mbsoftwaresoluti...@mbsoftwaresolutions.com wrote: On 2019-03-02 16:19, Kurt @ Gmail wrote: HA ha - Nice one Mike! Nope - its mainly FoxPro dev. in a logistics type dept. w/in UCLA. Downside - pay is TERRIBLE!!! Its a tad more than 1/2 my last salary! Ugh... I can't believe they want someone with Exp. - serious VFP/FoxPro exp. - yet, only want to pay 60K! Although, I hear this is common in Uni's! :-( Well, 60k in California is probably like 30k elsewhere, so sorry to hear that but at least you'll be working with a tool you love! [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/ba986753-5faa-dce6-941d-8a1743e3f...@optonline.net ** 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
On 2019-02-27 19:50, Eric Selje wrote: 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 What do you typically use, Eric? ___ 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/a34f24d2985230ff5778c8d1ef1de...@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: Creating a copy of a database -- best practice? - checking email - did not come through before
On 2019-03-02 08:14, Charlie-gm wrote:
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.
Hi Charlie,
I've got VFP available so COPY/APPEND PROCEDURES is available. So I
wrote a quick PRG and got the stored procedures just fine with
that...but the part that's missing now is the table-specific data like
default values (important as some call the usual newid('table') function
in the default PK field) and captions (not important).
--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/e6efbd4226dee2145628baff4f262...@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: UCLA & FoxPro...
On 2019-03-02 16:19, Kurt @ Gmail wrote: HA ha - Nice one Mike! Nope - its mainly FoxPro dev. in a logistics type dept. w/in UCLA. Downside - pay is TERRIBLE!!! Its a tad more than 1/2 my last salary! Ugh... I can't believe they want someone with Exp. - serious VFP/FoxPro exp. - yet, only want to pay 60K! Although, I hear this is common in Uni's! :-( Well, 60k in California is probably like 30k elsewhere, so sorry to hear that but at least you'll be working with a tool you love! ___ 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/750ce19e4408ffd62633ddc76b6a9...@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.
