>Imagine writing an app that shares a table and processes a lot of math calcs.
>Compile it and name it appA
>Compile it again and name it appB
>appA uses the top half of the table
>appB uses the bottom half of the table
>Run them both at the same time
>Will the apps take advantage of the dual core?

Sure, if you do it right <g>.
View the whole task as a multiuser scenario,
add a "lDone" flag to your record
add recordlocking to your app
and you can run even the same exe multiple times on one multicore or many networked machines.
That way it is abstracted into n-way, whereas you way would require (minimal) coding for quad core already.

Each process will be awarded CPU time distributed according OS priciples, perhaps "advised" via API or task manager.

HTH

thomas