Search results for query: *

I´m throughly testing the app, and rewriten all the dbase or DAO commands to VFP commands to send thru ODBC. I'm using this conection string: Driver={Microsoft Visual FoxPro Driver};SourceType=DBF;SourceDB=f:\data\basexport ;Exclusive=No Is there something wrong? The data is inserted from VB...

Thanks all forum members for your advice. Definitively I'll use the VFP ODBC. I've talked with my client and we are from one mind on this.

Luckyly, I'm using free tables with CDX. I tried the dbase driver approach just because it is the dafualt in a Windows installation. Thanks for clearing my doubts... I'd recommend a VFP ODBC driver to the client. Thanks

Thanks for your answers... Sorry for not answering before... The connection string that I'm using (and works) is: fox_conexion.ConnectionString = "Driver={Microsoft Visual FoxPro Driver};SourceType=DBF;SourceDB=C:\falconsight\csc\alf;Exclusive=No" the problema arises when I use...

I'm receiving data from another application, made with VB6. The records are written in free DBF tables (created with foxpro 26), thru ODBC. But, when we made the report queries -using another VFP-made app - not all the new data, show. If we reindex the CDX are updated, and the data displays. Is...

You can also use the expression: at([3000],memofieldname)>0 for evaluating inside the memo field and only work those that contain the desired data

I'm using free tables from another application, that will be feed from a VB application. I'm trying to connect to the database using de Microsoft dBase ODBC, buy receive this error: I have used VFP ODBC driver with no problem, buy I'd like to use the ODBC that comes in Windows XP as default...

Just my two cents. Use a parameter for this line CD("F:\Encounter") It is better to extract the value from a table or other easily modified source. Then if the path changes, you only change the value in a table, instead recompiling and redeploying all the app. Your code may look like this...

I'd recommend the second option from jrbbldr, using a recordset. It is because may be used widely, with almost any database, not only DBF.

Where there may be changes is in the SQL language syntax. If any query is giving you trouble use this If version() # "Visual FoxPro 07" set enginebehavior 70 endif to set the query behavior to the more open SQL flavor of VFP7. Use this before the queries to avoid conflicts.

Thanks for the aid... I've already found the problem in a recordset command

I'm using VB6 and the Crystal Reports controls that come with Visual Studio 6. My system runs WinXP SP2. My database is SQLServer 2005 I'm generating a report based on a view that already exists on the server. The query string that works goes like this: dim rsrepo as new ADODB.recordsource dim...

It crashes immediately after being called. Doesn't starts the installation welcome screen, and after going out, no other message. I assume its trying to change the registry, but it doesn't say a thing.

When I try to install a package done with Vb 6.0 deployment packager, I receive this error "error fatal no se puede generar el archivo de registro de operaciones de instalacion" ("Fatal error: could not generate installation registry operations file" or something like that) If I use the product...

Why don't simply use SELECT * FROM Temp GROUP BY acct_num order BY edwkey,open_dt1 ASC INTO cursor myCursorName readwrite ? That way you got the data in a fully editable form. Then you can use a SQL-select command directly in the cursor, that way filtering further your data as you like...

The data has been MARKED for deletion. The command "SET DELETED OFF" will indicate VFP not to use the deleted records on future queryes.

What do you need the JOIN for? You are selecting records just from the parent table. Also, ypu'll do better using a WHERE condition that filters on the exact records you want.

You guys must have a crystal ball...! This tip solved the problem I have in this moment...

Also remember than "type" is a VFP reserved word. It could cause unexpected results used as a field name. Especially if you try to copy or export the data to other files.

If that does not solve ypur trouble, consider using Set enginebehavior 70 to allow VFP work as it did in Version 7.0. That solves a lot of issues with the "improved" MS-Framework-Visual-Studio-compatible behavior.