sql-helper
Skill4 starsChanged 28 days agoMITView on GitHub
SQL Server integration patterns for Visual FoxPro applications. Use when writing SQL queries, working with SQL Pass-Through (SPT), troubleshooting database operations, or optimizing SQL Server calls.
3 other projects use a version of this.
Adopted by
Most recently taken up by
- aidankaokao/claude-skillstheir own version, first seen Oct 9, 2026
- bestdeejay-design/agent-skillstheir own version, first seen Aug 9, 2026
- kevinaimonster/skill-hubtheir own version, first seen Mar 18, 2026
Other versions3 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 3
- bestdeejay-design/agent-skills★ 6same name
- kevinaimonster/skill-hub★ 4same name
- aidankaokao/claude-skills★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository3 other files it gives its agents.
- debug-helperSkill
- form-editorSkill
- vfp-conventionsSkill
The file
We split this skill into the rules it gives an agent
1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 13
Always wrap SQL execution with error handling and retry logic:
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
SQL Helper for VFP + SQL Server
Core Rules
1. Use Safe SQL Execution
Always wrap SQL execution with error handling and retry logic:
*-- CORRECT - With error handling
FUNCTION example_sql_execute(tcSQL, tcCursor)
LOCAL lnResult, lnRetry
lnRetry = 0
DO WHILE lnRetry < 3
lnResult = SQLEXEC(gl_nSQLHandle, tcSQL, tcCursor)
IF lnResult >= 0
RETURN lnResult
ENDIF
lnRetry = lnRetry + 1
=INKEY(0.5) && Wait before retry
ENDDO
log_error("SQL failed after 3 retries: " + tcSQL)
RETURN -1
ENDFUNC
*-- WRONG - Raw SQLEXEC without handling
SQLEXEC(gl_nSQLHandle, "SELECT * FROM clients") && No error handling!2. Date vs Datetime (CRITICAL!)
| Prefix | SQL Type | VFP Function | Example |
d* | DATE | Date() | dbirthdate, ddeadline |
t* | DATETIME | Datetime() | tlogon, tcreated |
*-- CORRECT
m.dmodified = Date() && For DATE field
m.tlogon = Datetime() && For DATETIME field
*-- WRONG - Will cause "Conversion failed"
m.dmodified = Datetime() && ERROR! DATE field expects Date()3. Single T-SQL Batch for Multi-Step Operations
*-- CORRECT - One batch, one roundtrip
lcSQL = "SET NOCOUNT ON; " + ;
"DECLARE @newid INT; " + ;
"BEGIN TRY " + ;
" BEGIN TRANSACTION; " + ;
" INSERT INTO dbo.orders (cclient) VALUES ('ABC'); " + ;
" SET @newid = SCOPE_IDENTITY(); " + ;
" INSERT INTO dbo.orderitems (idorder) VALUES (@newid); " + ;
" COMMIT TRANSACTION; " + ;
" SELECT @newid AS newid; " + ;
"END TRY " + ;
"BEGIN CATCH " + ;
" IF @@TRANCOUNT > 0 ROLLBACK; " + ;
" SELECT -1 AS newid, ERROR_MESSAGE() AS errmsg; " + ;
"END CATCH"
example_sql_execute(lcSQL, "result")
*-- WRONG - Multiple roundtrips, risk of blocking
sql_begin_transaction()
example_sql_execute("INSERT INTO dbo.orders ...") && Roundtrip 1
example_sql_execute("INSERT INTO dbo.orderitems ...") && Roundtrip 2 - may block!
sql_commit_transaction() && Roundtrip 34. SET NOCOUNT ON - Required!
*-- CORRECT - NOCOUNT ensures you get the SELECT result
lcSQL = "SET NOCOUNT ON; UPDATE ...; INSERT ...; SELECT @id AS newid"
*-- WRONG - Without NOCOUNT, UPDATE returns empty result set
lcSQL = "UPDATE ...; INSERT ...; SELECT @id AS newid" && Result is empty!5. ROWLOCK for Multi-User
*-- CORRECT - Lock only the row, not the table
example_sql_execute("UPDATE dbo.sessions WITH (ROWLOCK) SET lactive = 0 WHERE idsession = 123")
*-- WRONG - May lock entire table
example_sql_execute("UPDATE dbo.sessions SET lactive = 0 WHERE idsession = 123")6. NULL Handling in Queries
*-- CORRECT - Use ISNULL or IS NULL
example_sql_execute("SELECT * FROM orders WHERE ISNULL(dshipped, '1900-01-01') < GETDATE()")
*-- Also correct - IS NULL check
example_sql_execute("SELECT * FROM orders WHERE dshipped IS NULL OR dshipped < GETDATE()")
*-- WRONG - NULL comparison always returns false
example_sql_execute("SELECT * FROM orders WHERE dshipped < GETDATE()") && Misses NULLs!7. Report Date Fields - CAST Required
ODBC returns SQL DATE as STRING in VFP. For reports, cast to DATETIME:
*-- CORRECT - For VFP reports
example_sql_execute("SELECT CAST(dbirthdate AS DATETIME) AS dbirthdate FROM dbo.persons", "rpt")
*-- WRONG - ODBC returns DATE as STRING, report formatting fails
example_sql_execute("SELECT dbirthdate FROM dbo.persons", "rpt")8. INSERT with IDENTITY Return (Multi-User Safe)
*-- CORRECT - SCOPE_IDENTITY is session-safe
FUNCTION sql_insert_get_identity(tcTable, tcFields, tcValues)
LOCAL lcSQL
lcSQL = "SET NOCOUNT ON; " + ;
"INSERT INTO dbo." + tcTable + " (" + tcFields + ") VALUES (" + tcValues + "); " + ;
"SELECT SCOPE_IDENTITY() AS newid"
example_sql_execute(lcSQL, "qryId")
RETURN qryId.newid
ENDFUNC
*-- WRONG - @@IDENTITY may return ID from trigger insert!
example_sql_execute("INSERT INTO dbo.orders ...")
example_sql_execute("SELECT @@IDENTITY AS id", "result") && May be wrong ID!9. sql_exec Return Value is Numeric
*-- CORRECT
IF example_sql_execute(lcSql, "result") < 0
log_error("Query failed")
ENDIF
*-- WRONG - Can't use ! operator on numeric
IF !example_sql_execute(lcSql) && ERROR! "!" expects logical10. String Escaping
*-- CORRECT - Escape single quotes
FUNCTION sql_quote(tcValue)
RETURN STRTRAN(tcValue, "'", "''")
ENDFUNC
lcSQL = "INSERT INTO notes (ctext) VALUES ('" + sql_quote(m.ctext) + "')"
*-- WRONG - SQL injection risk
lcSQL = "INSERT INTO notes (ctext) VALUES ('" + m.ctext + "')" && O'Brien crashes!11. Date Formatting for SQL
*-- CORRECT - ISO format works universally
FUNCTION sql_format_date(tdDate)
RETURN "'" + TRANSFORM(YEAR(tdDate)) + "-" + ;
PADL(MONTH(tdDate), 2, "0") + "-" + ;
PADL(DAY(tdDate), 2, "0") + "'"
ENDFUNC
*-- Usage
lcSQL = "SELECT * FROM orders WHERE dorder >= " + sql_format_date(DATE())
*-- WRONG - Locale-dependent, may fail
lcSQL = "SELECT * FROM orders WHERE dorder >= '" + DTOC(DATE()) + "'"Buffered Cursor Pattern
*-- Open with buffering
FUNCTION example_open_buffered_table(tcTable, tcCursor, tlReadWrite)
LOCAL lcSQL
lcSQL = "SELECT * FROM dbo." + tcTable
IF example_sql_execute(lcSQL, tcCursor) < 0
RETURN .F.
ENDIF
IF tlReadWrite
=CURSORSETPROP("Buffering", 5, tcCursor) && Optimistic table buffering
=CURSORSETPROP("Tables", "dbo." + tcTable, tcCursor)
=CURSORSETPROP("KeyFieldList", "id" + tcTable, tcCursor)
=CURSORSETPROP("UpdatableFieldList", "*", tcCursor)
=CURSORSETPROP("UpdateNameList", ..., tcCursor)
=CURSORSETPROP("SendUpdates", .T., tcCursor)
ENDIF
RETURN .T.
ENDFUNC
*-- Save changes
FUNCTION sql_tableupdate(tcCursor)
IF !TABLEUPDATE(.T., .F., tcCursor)
=TABLEREVERT(.T., tcCursor)
RETURN .F.
ENDIF
RETURN .T.
ENDFUNC
*-- Close (auto-saves if dirty)
FUNCTION example_close_cursor(tcCursor)
IF USED(tcCursor)
IF CURSORGETPROP("Buffering", tcCursor) > 1
=sql_tableupdate(tcCursor)
ENDIF
USE IN (tcCursor)
ENDIF
ENDFUNCQuick Reference
| Function | Purpose | Example |
SQLCONNECT() | Connect to SQL Server | gl_nHandle = SQLCONNECT("DSN") |
SQLEXEC() | Execute SQL | SQLEXEC(handle, sql, cursor) |
SQLDISCONNECT() | Close connection | SQLDISCONNECT(handle) |
SQLSETPROP() | Set connection property | SQLSETPROP(handle, "QueryTimeOut", 30) |
SQLGETPROP() | Get connection property | SQLGETPROP(handle, "ConnectString") |
CURSORSETPROP() | Set cursor property | CURSORSETPROP("Buffering", 5, cursor) |
TABLEUPDATE() | Save buffered changes | TABLEUPDATE(.T., .F., cursor) |
TABLEREVERT() | Discard changes | TABLEREVERT(.T., cursor) |
Common Errors
| Error | Cause | Solution |
| "Conversion failed date/time" | Datetime() for DATE field | Use Date() for d* fields |
| "Lock request time out" | Another session blocking | Use ROWLOCK, single batch |
| Error 1492 "No key columns" | Missing KeyFieldList | Set primary key in cursor props |
| Empty result after UPDATE | Missing SET NOCOUNT ON | Add SET NOCOUNT ON at start |
Resources
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

