Oh, I see. I didn't understand it that way.

I had thought more like this: for example, the number of screens would only apply...

Yes, in a many to many relationship, you would need to have the 3rd table. I just did not understand from the Original Poster that this was a many to many...

I like the idea of a Miscellaneous table, but I am not sure you need the third table to join them. Just include the Client_ID as a foreign key field...

In spite of what I stated in my last message, I agree with you. I don't believe I have a single variant field...

Another option would be to put the "extra" fields in a separate table linked by the key in the first table. That way you could have as many new pieces...

Whether or not the user can insert records depends on the SQL security. If the user can insert records using Enterprise Manager or SSIS, then they can insert records in...

We do our SQL backup to disk and then back that up to tape. That makes a restore much easier (and backups as well). You can use SQL backup to...

The shrink database task in the maintenance plan works, but the task to back up the transaction log does not behave in a consistent manner. When you tell it to...

The log will not truncate after a full backup unless you also back up the transaction log. Backing up the transaction log, should cause the log file to shrink.

However,...

I have encountered the same problem. When I use the Maintenance Wizard, it works fine for the backups, but does not work for the transaction logs. If you select "all...

Sugesh,

I understood that executing an SSIS package is not part of the client component in SQL 2005.

I have installed the client on a machine, but it is not possible to...

Hi Mohamed,

If you are looking to have a live connection, as opposed to a connection to a database on the mobile device, then in your C#.net Smart Device project, just...

Have you tried executing the process with just a few records? That way you would know whether it was the number of records or not.

Check to make sure that you did not uncheck the "Allow Nulls" column. Since the table already has data in it, you will not  be able to require an entry...

I saw that problem when I had moved the SQL 2000 jobs to a different server and had NOT opened them in enterprise manager and saved them on that server....