<t>Your application looks pretty specialized, rather than being an application everyone might use. That being the case, one would think that anyone who needed such an application would be quite willing to download it. I realize that if you made it web-based then it would be cross platform and so ope...

<t>My general approach to data (remote or otherwise) has been to set up an object hierarchy in which each object maintains its own data. I work for a school, so we have families who have students on our program, who then have grade levels, which have courses, which have quarters, which have individu...

<t>I use parameterized queries from Foxpro to Postgres in my programs all the time. If you've got that working it's really good news. I also appreciate setting recno at 1, since I've had to issue Goto 1 commands to get that done so far.<br/> <br/> I thought my application was pretty big, but it's on...

Just out of curiosity ... what enhancements were you able to make in the SQL functions?

<t>Considering that Foxpro MEM files are more like temporary files than permanent data, I don't think you need to be at all concerned whether XSharp MEM files are Foxpro compatible. As long as memory variables of whatever type can be saved from XSharp programs and then restored to XSharp programs, f...

I have only used SqlExec with Postgres, not with SQL Server. However, with postgres you set data options like that through the ODBC driver setup.

I didn't know about the phantom button. I assume you can't click it because it's located off-screen.

The GetPrinter dialog should have a properties button, though, so if you're recreating it I'd say definitely include it.

<t>I noticed that the XSharp documentation for COPY TO ARRAY says "The default is all fields with the exception of memo fields, unless the command supports the MEMO clause." In FoxPro COPY TO ARRAY does not support the MEMO clause. If XSharp's implementation of COPY TO ARRAY will have support for in...

You're right, ICASE doesn't give an error in a new program. Maybe what I'm seeing is a cascade from other errors.

<r>Do conditions used in ICASE need to have parentheses around them? It seems like they do, but I wonder if I'm just doing something wrong. <CODE><s>[code]</s><i> </i>lcdiplomatype=ICASE((eid_retval="G"),"General",(eid_retval="A"),"Advanced",(eid_retval="N"),"Non-Diploma","Standard") //no error lcdi...