Same concept...

          Column1               Column2            Subtotal for row

          text1                    text2               =val(text1) + val(text2)

          text3                    text4               =val(text3) + val(text4)

Grand total for columns

=val(text1) + val(text3)     =val(text2) + val(text4)

so on, etc, etc.

If you're working in Access, in the form itself, why not just add the logic to the summary text box like so...

Control Source:  =Val([text1])+Val([text2])

This seems more like a presentation layer problem -- can't you simply add the two columns in the form for the totals.  If you need this information in the table,...

Does the server have access to the text file / directory?

You can use sp_defaultdb to set the default database for a user.

Syntax:  sp_defaultdb 'login_name','database'

You should be able to create a cursor with

SELECT * FROM master..sysxlogins

and then loop...

Your view of Access is right.  It's much more efficient to house your data in SQL Server.  We use Access a lot as a front-end to build forms that access data...

I use EM alot to build my queries, because it is alot like the MS-Access query interface.  After I have the query built, I will usually copy the SQL and...

Never looked at it like that, but that's a great outlook on life.  I'm going to try to use that myself.

I believe the pop-up box gives the explanation:

Choose Target Table for Insert From

An INSERT FROM inserts rows from the selected source(s) into only one table or inline function.

The selected sources...

Select "Design Table" and then you will be able to add a column to the table definition

When this happens with our server, it is usually do to some long running, resource intensive process.  We use sp_who & sp_who2 to see what is running when EM becomes...

You also have Case statements...

CASE WHEN criteria_1 THEN result_1

         WHEN criteria_2 THEN result_2

         WHEN criteria_3 THEN result_3

         etc

         ELSE result_n

END

Along the script lines, we run the following task which records the size of all databases in a table.  This could then be queried and if a critical size has...

I believe the way the query was written, ON and WHERE could have been used interchangeably.  Concerning CASE statements, you have to use IIF in Access.

Instead of checking permissions, you might simply handle the error (if it occurs) within the application itself.