Why doesn't VFP program work on my computer??

[Olimits7]

Hello,

I have a VFP program that I use to work on order fulfillment for my website, but I have an issue with it.

I currently have a programmer working on a VFP program that handles order fulfillment on my website. He made some changes to it and the VFP program works fine on his computer. But then when he sends me all the files including the *.exe file it doesn't work on my computer properly.

Does anyone know why this would happen??

I don't understand this since we both have the same exact files on both computers and are both running Windows XP. It seems like VFP is very unstable for it to work on 1 machine and not the other.

Thank you,

olimits7

 

[Ed Andres]

Um, you will have to be more specific than "it doesn't work on my computer".

What doesn't work?
Are there error messages?
What are the XP service pack levels? - there is a new service pack out for XP.
What version of VFP including service pack?



Ed

 

[Olimits7]

Sorry, I should have been more descriptive.

The part that doesn't work is the import process of when my VFP connects to my website via ODBC and imports the orders.

No error messages but the 2 things that don't work on my computer but work fine on his computer when he runs the VFP program are:

1. The customer name imports fine, but on my computer it just shows an empty field.
2. The enrypted credit card & CVV numbers import and show fine on the "payment" screen, but on my computer the numbers are all messed up and don't show valid numbers just characters.

So it seems to be something with the import function, but if the import function works fine on his end it should also work fine on my end, right??

I have SP2 installed on my maching, and I think he has the same on his but I will double check and ask him. But do you think that the SP could be causing these issues??

The VFP program is being compiled with VFP 8, and he is just sending me the *.exe file and all the data and other files needed to make the *.exe run properly.

Thank you,

olimits7

 

[Olaf Doschke]

What's the remote database and what ODBC driver do you use? If it's eg MySQL the retrieved data can depend on some ODBC settings you have different on your computer.

If it's SQL Server, yesterday I changed connectionstring fomr Driver=SQL Native Client to Driver=SQL Server, because SQL Native Client retrieves Varchar(MAX) according to the first record it finds, if that is NULL or empty I get a C(0) field type. With SQL Server ODBC Driver I always get a Memo field in the result.

Bye, Olaf.

 

[Olimits7]

Hi,

The remote database on my webserver is a mySQL database, and I think the VFP program uses the "MySQL ODBC 3.51 Driver" to connect to my database.

That could be a possibility that we have different ODBC settings on each computer. Where can I see and change these ODBC settings you are talking about on my computer??

Thank you,

olimits7

 

[ashmac2]

Control Panel - Administrative Tools - Data Sources (ODBC)

 

[Olimits7]

I talked to my programmer and he told me all the ODBC information is saved in the code; so I don't think that my ODBC settings would have any effect on the VFP program.

Does anybody else have any other ideas on what could cause this to not work on my machine??

Thank you,

olimits7

 

[Olaf Doschke]

Can you post the connection string used in the program?
If it lacks a part OPTION=<<Some Number>>, the odbc driver configuration can have an effect, especially the one you experience, eg column widths are wrong or even 0 on the vfp side.

http://dev.mysql.com/doc/refman/5.0/en/myodbc-configuration-connection-parameters.html

You should have the bit 0 (value 1) set - Don't optimize column width. Also bit 9 (value 512) - Pad char to full length.

VFP is sensitive to such options as the first record of the resultset will determine the result cursor structure. If that has null or an empty string the result cursor may be defined as C(0), like I experienced with SQL Server.

Bye, Olaf.

 

[Olimits7]

Hi,

The connection string that I'm using is:

"driver={mysql odbc 3.51 driver};" + ;
"SERVER=" + ;
lcserver + ";" + ;
"PORT=3306;" + ;
"DATABASE=" + ;
lcdatabase + ";" + ;
"USER=" + lcuser + ;
";" + "PASSWORD=" + ;
lcpwd + ";" + ;
"OPTION=3;"

Thank you,

olimits7

 

[Olaf Doschke]

Well, try with OPTION=515

 

[Olaf Doschke]

VFP Wiki suggests OPTION=262657

http://fox.wikis.com/wc.dll?Wiki~VFPCommandSQLStringConnect~VFP

That is MYODBC_NO_TRANS (262144)+ MYODBC_PAD_CHAR (512)+ MYODBC_NO_COL_WIDTH_OPTIMIZE (1)

Having read their meaning I'd also add MYODBC_BIGINT_TO_INT (16384) and MYODBC_RETURN_MATCHING_ROWS (2) and make it 0x44203 = 279043.

Bye, Olaf.

 

[Olimits7]

Hi,

1. If this import works fine on my programmers's computer and he is using the same option 3 as me, would it really matter if I change this option field??

2. What do options 515 and 262657 stand for??

Thank you,

olimits7

 

[Olaf Doschke]

1. You're right that this would not matter if that was so.

2. 515 and 262657 are a sum of several options. the OPTION=xyz option is really a set of options you can also set visually.

The link to mySQL documentation I gave above explains these options rather well...

http://dev.mysql.com/doc/refman/5.0/en/myodbc-configuration-connection-parameters.html

If you don't try the suggestion you will not find out if it matters or not.

Having similar OS and files is leaving much room for differences on your and his computer. You do have the same odbc driver version installed?

You say you get crumbled credit card & CVV numbers. Looks like they are encrypted, which is fine of course, as it secures that sensitive data, but then some part of the code is missing decrypting those informations. Sounds like there are still differences in yours and his version of the code.

Bye, Olaf.

 

[Olimits7]

Hi,

Thank you everyone for your help. I finally got it working now.

I don't know what exactly fixed it, but I ended up uninstalling/reinstalling the following: FoxPro 8, runtime files, and mySQL ODBC 3.51 driver.

So I'm guessing one of the things I did above fixed this issue.

Thank you again,

olimits7

 

[Olaf Doschke]

Glad you got it working.

Bye, Olaf.