ProFox

profox@leafe.com

2704 discussions

Grids (Not Really)
by Gene Wirchenko 20 Apr '18

20 Apr '18

Hello: I have tried about four times to post regarding grids. I wonder if such posts are being filtered. Sincerely, Gene Wirchenko

2 1

Re: INSERT INTO...SELECT Issue
by Gene Wirchenko 19 Apr '18

19 Apr '18

At 13:32 2018-04-19, Ted Roche <tedroche(a)gmail.com> wrote: [snip] >Unsurprisingly, ODBC thinks it's a dumb name for a field, too. > >You'll probably need to "escape" it. I'm decades out of ODBC, so I >don't recall if ODBC wants you to enclose the field name in single >quotes, square brackets or back ticks (that `` funny key in the upper >left corner no one ever uses). A web search might yield a suggestion, >or you can just try the Usual Suspects... Or maybe double-quotes. Or maybe, doubled single-quotes (like ''this''). Or maybe escaped quotes (of various sorts) such as '\"'. Isn't it nice to have options? <GD&RVVF> That funny key is used in UNIX. Sincerely, Gene Wirchenko

1 0

INSERT INTO...SELECT Issue
by Paul H. Tarver 19 Apr '18

19 Apr '18

I posted a longer version of this situation previously, but it may have been mis-titled or included too much detail because I've gotten no responses. Here's the low down and dirty version: When you use INSERT INTO.SELECT from a remote data source that includes fieldnames that begin with numbers in the development environment, VFP9 automatically changes the leading digit in the field name to an underscore ('_'). However, when executing the same command as a compiled executable this automatic substitution does not occur and VFP will allow fieldnames with a leading digit to be returned in the resultant cursor. This causes major problems later if you use the remote data cursor to create a new cursor because Foxpro won't allow field names with a number in the first position. ALTER TABLE cannot be used on the remote data cursor and even if you make the cursor READWRITE, the length of the fieldnames can often exceed 10 characters. My question is this: Has anyone here run into this issue and if so, Is there any another way or procedure around this situation that would allow me to manually fix the fieldnames which start with a number assuming I have no way to change the source data. Thanks in advance. Paul --- StripMime Report -- processed MIME parts --- multipart/alternative text/plain (text body -- kept) text/html ---

6 17

[NF] What is new with mySQL ver 8
by Stephen Russell 19 Apr '18

19 Apr '18

Event Registration is required. MySQL 8.0 is the newest version of MySQL. Filled with many new features, it is one of the most impressive releases to date. Join Mike Frank, MySQL Product Manager, to learn more about the new NoSQL Document Store, and the many changes and enhancements with Data Dictionary, Roles, Unicode, CTEs, Window Functions, Security, Replication, SysSchema, GIS, and much more. https://event.on24.com/eventRegistration/EventLobbyServlet?target=reg20.jsp… For anyone who is considering how relational and NoSQL can work together. -- Stephen Russell Sr. Analyst Ring Container Technology Oakland TN 901.246-0159 cell --- StripMime Report -- processed MIME parts --- multipart/alternative text/plain (text body -- kept) text/html ---

1 0

"Cannot load 32-bit DDL wwipstuff.dll"
by Ted Roche 19 Apr '18

19 Apr '18

Someone in the office hit this today. Win10, 674-bit fully updated. This project has been running fine. The project crashed this morning and had to be rebuilt and only now does the above error show up. What's the most likely thing you'd check? The DLL's in the path. -- Ted Roche Ted Roche & Associates, LLC http://www.tedroche.com

5 7

Re: [TEST] Sent message twice yesterday and it didn't get posted
by Gene Wirchenko 17 Apr '18

17 Apr '18

At 11:17 2018-04-17, Ed Leafe <ed(a)leafe.com> wrote: >On Apr 17, 2018, at 1:12 PM, Gene Wirchenko <genew(a)telus.net> wrote: > > > >> > Just checking and wondering why my earlier messages didn't post. > >> > >> Caught in the spam filter, for some reason. > > > > What about mine? I have twice now tried to post about grids > and both times, it did not get posted. You also did not reply to my E-mails. > >https://leafe.com/archives/msg/510703 Interesting. I did *not* get that message. This is bothersome especially when I have needed help. I am not aware of missing any other messages (non-ProFox). Sincerely, Gene Wirchenko

1 0

Re: [TEST] Sent message twice yesterday and it didn't get posted
by Gene Wirchenko 17 Apr '18

17 Apr '18

At 07:16 2018-04-17, you wrote: >On Apr 17, 2018, at 8:44 AM, Paul H. Tarver <paul(a)tpcqpc.com> wrote: > > > Just checking and wondering why my earlier messages didn't post. > >Caught in the spam filter, for some reason. What about mine? I have twice now tried to post about grids and both times, it did not get posted. You also did not reply to my E-mails. Sincerely, Gene Wirchenko

2 1

VFP9 - Save as XLSX
by Desmond Lloyd 17 Apr '18

17 Apr '18

Good Morning, Need to be able to copy the contents of a cursor to an Excel file, but it needs to be in the xlsx. Am a newbie to Excel Automation and have read that you can saveas, and it will save in the latest format. Well mine doesn't. oworkbook.version shows 16. (we are running Office 365) Tried the SweetPotato method but it errors out. Not sure why. Would someone be kind enough to point me in the right direction, with some possible examples... TIA, Desmond --- StripMime Report -- processed MIME parts --- multipart/alternative text/plain (text body -- kept) text/html ---

12 24

[TEST] Sent message twice yesterday and it didn't get posted
by Paul H. Tarver 17 Apr '18

17 Apr '18

Just checking and wondering why my earlier messages didn't post. Paul --- StripMime Report -- processed MIME parts --- multipart/alternative text/plain (text body -- kept) text/html ---

2 2

AppendXLSX.prg - Difference In Development & Executable
by Paul H. Tarver 17 Apr '18

17 Apr '18

I have been using AppendXLSX.prg written by Craig Boyd for many years with great success. Until now. Last week, I was training a client on some software but when I tried to import an Excel file (which I had done at least a hundred times on the project in development mode), it failed and I got an error about a missing ') '. Nothing I tried would work and so I asked them to use CSV files in the interim until I could get the problem figured out. After extensive review, I traced the error to this line in Craig's code: INSERT INTO (m.tvWorkarea) (&lcFieldList) SELECT &lcNvlFieldList FROM (m.lcSQLAlias) WHERE &tcTableForExpr I tested importing the client spreadsheets multiple times on my development machine and every time, AppendXLSX.prg would work perfectly in development mode and fail in same spot when run as part of my executable program. I added lots of messagebox items to see the values of the compiled code and eventually I changed the INSERT INTO line above to a TEXT..ENDTEXT command so I could store the fully expanded command as a string and save the string to a file to do in-depth comparisons between development and compiled versions. When I compared the expanded commands character by character, I realized the client had a column header in their spreadsheet which started with a number: '3RDPARTY' and the INSERT TO was failing in executable mode because FoxPro doesn't allow field names that start with a number. But I still couldn't explain why the same code worked in development mode. After working my way back through the code, I found prior to the INSERT INTO command mentioned above, Craig issues the following command to retrieve data from the Excel worksheet: m.lnResult = SQLEXEC(m.lnSQL,[SELECT ] + m.tcExcelFieldList + [ FROM "] + m.tcSheet + [" Where ] + m.tcExcelWhereExpr, m.lcSQLAlias) And this is where it gets weird. When this command is issued from within the development environment, the the column header '3RDPARTY' is automatically changed to '_RDPARTY' BUT this automatic substitution DOES NOT occur when the command is issued from within a compiled EXE and the column name remains '3RDPARTY' which then causes a failure in the INSERT INTO command which occurs after the remote table has been created. I tried just renaming the field name prior to the INSERT INTO command, but this creates a field not found error. I tried ALTER TABLE after the cursor is returned from the SQLEXEC command, but the command failed because the initial cursor is a remote table. After trying to make the initial cursor a READWRITE cursor it failed again because there are field names larger than 10 characters. My client's files are created with automated processes and reflect the fieldnames within their software datastore. I do not have access to change these variable names. However, I need some suggestions for potential workarounds short of having the client manually rename the column each time they create the file. Ideally, I'd like to come up with a solution that would be work in all cases for all clients but that may be too much to hope for. Sorry this is so long, but I wanted to include all I learned today about this problem. Any thoughts? Paul --- StripMime Report -- processed MIME parts --- multipart/alternative text/plain (text body -- kept) text/html ---

1 0

Jump to page:

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

ProFox