Some key GoToAssist functions weren't working and the network people determined that Windows User Account Control Security was the culprit and disabled it.

That made all my issues go away too.

I'll still go ahead and remove all the ALTER TABLES though. I never liked them.




>Bill,
>
>Another known issue of "alter table" against a cursor is that it won't work if field names have more than 10 characters. The "select" probably is safest because it insulates you from VFP's behind-the-scenes decisions about whether a cursor should be file- or memory-based. We don't want to have to worry about that stuff!
>
>Re dropping columns- Deleting array rows would work.. or you could create a temporary dbc against the target tables, then create a dbc view, remove the fields, and harness the resulting SQL. Or if the app has a dbc you could add this view to it and just USE myview to deliver a cursor without further ado.