agentleFS
GSG-DevsGSG-Devs/claude-vfp-skills/skills/debug-helper/SKILL.md

debug-helper

Skill4 starsChanged 28 days agoMITView on GitHub

Debugging guide for Visual FoxPro applications. Use when troubleshooting errors, analyzing logs, investigating SQL blocking issues, or diagnosing runtime problems.

1 other project uses a version of this.

Adopted by

Most recently taken up by

  • Other versions1 project uses a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    Wrote their own version · 1

    1. mosaic-platform/skills★ 1same 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.

The file

We split this skill into the rules it gives an agent

2 rules. About 0 are common, 1 is distinctive, and 1 is 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.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Use ROWLOCK hint: UPDATE table WITH (ROWLOCK) SET ...

    line 101
  2. Distinctive:

    Use single T-SQL batch instead of multiple calls

    line 102

≈ “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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

VFP Debug Helper

Common Errors and Solutions

"Conversion failed when converting date and/or time"

Cause: Using Datetime() for a DATE field (prefix d*)

*-- WRONG
m.dbirthdate = Datetime()  && DATE field expects Date()!

*-- CORRECT
m.dbirthdate = Date()      && DATE field
m.tcreated = Datetime()    && DATETIME field

"Unrecognized command verb"

Cause: Using ELSEIF which doesn't exist in VFP

*-- WRONG - VFP has no ELSEIF
IF x > 10
    y = 1
ELSEIF x > 5   && ERROR!
    y = 2
ENDIF

*-- CORRECT - Use DO CASE
DO CASE
CASE x > 10
    y = 1
CASE x > 5
    y = 2
ENDCASE

"Operator/operand type mismatch"

Common causes:

  1. Comparing NULL values:
*-- WRONG
IF ddeadline < DATE()  && Fails if NULL

*-- CORRECT
IF VARTYPE(ddeadline) = 'D' AND ddeadline < DATE()
  1. Using ! on non-logical:
*-- WRONG - sql_exec returns numeric, not logical
IF !sql_exec(lcSQL)

*-- CORRECT
IF sql_exec(lcSQL) < 0

Error 1492 "No key columns"

Cause: TABLEUPDATE() can't identify which record to update

Solution: Set cursor properties correctly:

=CURSORSETPROP("KeyFieldList", "idclient", "qryClients")
=CURSORSETPROP("UpdateNameList", "idclient dbo.clients.idclient, cname dbo.clients.cname", "qryClients")
=CURSORSETPROP("Tables", "dbo.clients", "qryClients")
=CURSORSETPROP("SendUpdates", .T., "qryClients")

"Lock request time out period exceeded"

Cause: Another session is blocking the table/row

Diagnosis:

-- Find blocking sessions
SELECT
    r.session_id,
    r.blocking_session_id,
    r.wait_type,
    r.wait_time,
    s.login_name,
    s.host_name,
    s.program_name
FROM sys.dm_exec_requests r
JOIN sys.dm_exec_sessions s ON r.session_id = s.session_id
WHERE r.blocking_session_id > 0

Solutions:

  1. Use ROWLOCK hint: UPDATE table WITH (ROWLOCK) SET ...
  2. Use single T-SQL batch instead of multiple calls
  3. Keep transactions short
  4. Implement connection cleanup for abandoned sessions

"Variable not found"

Common causes:

  1. Missing m. prefix with SCATTER:
SCATTER MEMVAR
*-- WRONG
? cname

*-- CORRECT
? m.cname
  1. Scope issue:
*-- LOCAL variable not visible in called function
LOCAL lcValue
lcValue = "test"
=SomeFunction()  && Can't see lcValue

*-- Solution: pass as parameter or use PRIVATE

"File is in use"

Cause: Table or file already open

*-- Check if already open
IF USED("mytable")
    SELECT mytable
ELSE
    USE mytable
ENDIF

*-- Or use alias safely
USE mytable IN 0 ALIAS newalias

Debugging Techniques

Check Variable Type

? VARTYPE(myvar)
&& Returns: C=Char, N=Numeric, D=Date, T=DateTime, L=Logical, O=Object, U=Undefined, X=NULL

List Open Tables/Cursors

LOCAL laUsed[1], i
=AUSED(laUsed)
FOR i = 1 TO ALEN(laUsed, 1)
    ? laUsed[i, 1], laUsed[i, 2]  && Alias, WorkArea
ENDFOR

Check Cursor Properties

? CURSORGETPROP("Buffering", "mycursor")
? CURSORGETPROP("KeyFieldList", "mycursor")
? CURSORGETPROP("UpdateNameList", "mycursor")
? CURSORGETPROP("Tables", "mycursor")
? CURSORGETPROP("SendUpdates", "mycursor")

List Open Forms

LOCAL i
FOR i = 1 TO _SCREEN.FormCount
    ? _SCREEN.Forms[i].Name, _SCREEN.Forms[i].Caption
ENDFOR

Error Object Details

TRY
    *-- Code that might fail
CATCH TO loEx
    ? "Error:", loEx.ErrorNo
    ? "Message:", loEx.Message
    ? "Procedure:", loEx.Procedure
    ? "Line:", loEx.LineNo
    ? "LineContents:", loEx.LineContents
    ? "Details:", loEx.Details
ENDTRY

SQL Session Debugging

Check Current SPID

example_sql_execute("SELECT @@SPID AS spid", "qrySpid")
? "Current SPID:", qrySpid.spid

Find Active Sessions

SELECT
    session_id,
    login_name,
    host_name,
    program_name,
    status,
    open_transaction_count,
    last_request_start_time
FROM sys.dm_exec_sessions
WHERE program_name LIKE '%YourAppName%'
ORDER BY last_request_start_time DESC

Find Blocking

SELECT
    t1.session_id AS blocked_session,
    t1.blocking_session_id AS blocking_session,
    t1.wait_type,
    t1.wait_time / 1000.0 AS wait_seconds,
    DB_NAME(t1.database_id) AS database_name
FROM sys.dm_exec_requests t1
WHERE t1.blocking_session_id > 0

Kill Stuck Session (Use Carefully!)

-- First verify it's safe to kill
SELECT * FROM sys.dm_exec_sessions WHERE session_id = 123

-- Kill if safe
KILL 123

Logging Best Practices

Simple Log Function

FUNCTION log_error(tcMessage)
    LOCAL lcFile, lcLine
    lcFile = "Logs\" + DTOS(DATE()) + "_error.log"
    lcLine = TRANSFORM(DATETIME()) + " | " + tcMessage
    =STRTOFILE(lcLine + CHR(13)+CHR(10), lcFile, .T.)
ENDFUNC

Log with Context

FUNCTION log_debug(tcMessage, tcProcedure)
    LOCAL lcFile, lcLine
    lcFile = "Logs\" + DTOS(DATE()) + "_debug.log"
    lcLine = TRANSFORM(DATETIME()) + " | " + ;
        IIF(EMPTY(tcProcedure), "", "[" + tcProcedure + "] ") + tcMessage
    =STRTOFILE(lcLine + CHR(13)+CHR(10), lcFile, .T.)
ENDFUNC

Search Logs

# Find errors in log files
grep -r "ERROR" Logs/

# Find specific error
grep -r "Conversion failed" Logs/

# Recent entries
tail -50 Logs/20240115_error.log

Performance Debugging

Check Index Usage

-- Show missing indexes
SELECT
    OBJECT_NAME(d.object_id) AS TableName,
    d.equality_columns,
    d.inequality_columns,
    d.included_columns,
    s.user_seeks,
    s.user_scans
FROM sys.dm_db_missing_index_details d
JOIN sys.dm_db_missing_index_groups g ON d.index_handle = g.index_handle
JOIN sys.dm_db_missing_index_group_stats s ON g.index_group_handle = s.group_handle
WHERE d.database_id = DB_ID()
ORDER BY s.user_seeks DESC

Identify Slow Queries

SELECT TOP 10
    SUBSTRING(t.text, (s.statement_start_offset/2)+1,
        ((CASE s.statement_end_offset
            WHEN -1 THEN DATALENGTH(t.text)
            ELSE s.statement_end_offset
        END - s.statement_start_offset)/2) + 1) AS query_text,
    s.execution_count,
    s.total_elapsed_time / 1000000.0 AS total_seconds,
    s.total_elapsed_time / s.execution_count / 1000.0 AS avg_ms
FROM sys.dm_exec_query_stats s
CROSS APPLY sys.dm_exec_sql_text(s.sql_handle) t
ORDER BY s.total_elapsed_time DESC

Quick Diagnostic Checklist

  • Check error number and message
  • Verify variable types with VARTYPE()
  • Check if tables/cursors are open with USED()
  • Verify cursor buffering properties
  • Check SQL connection with SQLGETPROP()
  • Look for blocking sessions
  • Review recent log entries
  • Test with simplified code

Resources

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.