Programming & Development
I like to create things. When I was 13, I became interested in computers and the internet.
I wanted to convert a particular research project I had been working on into a webpage,
so I checked out a book about HTML from the library. By age 14, I knew all the basics of html
and was beginning to learn BASIC for simple school math calculations.
I liked programming, but realized
that BASIC's usefullness was limited to Dos-like applications. Upon the suggestion of a friend and mentor,
I graduated to Visual Basic (6.0) and started reading everything I could find about the language and programming practices in general.
By the age of 16, I had written several little applications to automate a variety of tasks ranging from
solving quadratic equations to generating powerpoint presentations.
I currently know and use on a regular basis:
Visual Basic 6.0, VBA, VB.NET
HTML, CSS, JavaScript
ASP, ASP.NET 2.0
ADO, ADO.NET, SQL
XML/XSL, XSLT
C++, C#
Visual FoxPro
|
|
|
|
|
|
 Saturday, October 21, 2006 |
Spent about 2 hours last night throwing together a contraction timer app that will run on my Verizon XV6700 smartphone. It will be handy not having to remember or write down the length of the contractions and time between and all that...and it will be cool having a log of all her contractions. |
jeremy at 5:09 AM |
(0) Comments
|
Add a comment |
Permalink
|
|
|
|
|
Tuesday, October 17, 2006 |
Here's an example of a very useful, but not well-known sql statement that will update a field in a table using a value from another table where both records are referenced by a common key
update tableOne set tableOne.field1=tableTwo.fieldX from tableOne, tableTwo where tableOne.commonID=tableTwo.commonID |
jeremy at 1:50 AM |
(0) Comments
|
Add a comment |
Permalink
|
|
|
|
|
Thursday, October 12, 2006 |
| Foxpro stored procedures from .NET |
|
I was recently faced with the task of integrating a .net web application with a foxpro database. Due to the specific requirements of the project, the integration had to be written in a .net language. Even though the integration was just performing CRUD operations (create, read, update, delete), at several points during the design phase, I kept thinking "Man, this would be easier in foxpro!". In some cases, an operation that would take .net 10 lines of code could be accomplished in just 3 lines of FoxPro.
After much research and experimentation, it turns out the FoxPro OleDb driver will allow you to call stored procedures that are actually foxpro .prg files! Essentially, you can create functions or procedures in foxpro, call the program from the .net app (using standard sql syntax and passing any parameters necessary), and return values to the .net app as needed. This opens the door to many interesting possibilities... |
jeremy at 2:05 AM |
(0) Comments
|
Add a comment |
Permalink
|
|
|
|
|