>What better way to connect to a networked table?
>
>I'm used to just sharing these tables by setting table property, and putting the table on our shared networked drive.

That's what I have been doing, and it works. Connecting to a database server gives you better data security, and it can improve performance, but it would also require a major redesign - unless, of course, the database system were designed from the very beginning taking client-server into account.
>
>I have never tried SQL. If in case I would use the SQL, what things do I need and how to perfectly command my programs to connect to them?
>
>Also, is there any command to actually convert standard foxpro programs to web-based ones like this UT?

A relatively simple way - as it seems to me, as an outsider without practical experience - is connecting to the remote database with a remote view. Other methods - like SQL Pass-Through - are supposed to be more efficient, but the main problem at first may be to do the transition quickly.

There is no single command to change to client-server; you may need a major redesign. For a start, you can no longer open a table and use the "Seek" command - local views or remote views don't have permanent indexes. So if your program logic relies heavily on this (as some of my procedures do), you will need to redesign those parts.