Hi,

I was able to solve the problem by getting some pieces of info from different articles. I saved the file name filename_yyyymmdd_1

(1 is the sequence) in a db table every...

I can get the sequence from the database using a function or I can run a stored procedure to create the file and store it in a table and then...

The problem was due to ODBC tracing was set on by the network admin on the server. Once the tracing stopped, everything back to normal.

Maybe it's started. Did you try connecting to master from QA?

From the command prompt type

sqlservr.exe -c -m -T3608

(You have to switch to the binn directory where sqlservr.exe resides, unless it's in your path. Normally it's in

C:\Program Files\Microsoft SQL Server\MSSQL\Binn)

And...

itay,

how are you starting? from EM or command prompt? For some reason setting the startup parameters in EM didn't do anything. It works from command prompt

Liliya,

Thank you so much for your information. With your information I could have migrated the replication to the new server , but our management decided to keep the old server...

During the times the Windows crashed, no backups were done. So I don't think the backups were causing the issue for us.

You can create a sp in sql server to import the data using t-sql or DTS package. Then you can call this sp from Access using an OLEDB connection. I...

When the networks are not trusted, you cannot use windows authentication. You have to use SQL authentication.

Excellent article

Microsoft will never take VB.Net away. They may improve it. It's still more user friendly than C# and the code is better readeable, but C# is more powerful in the .NET world.

I would take either VB.NET or C# to use with SQL Server for the following reasons.

1. Both are Micorosft products so more features are available.

2. Uses less development time.

3. OOD.

4....

We never had any performance problems with drop down lists with ODBC connections. We use the DSN-less connection to SQL Server.

If your Access query contains many joins or multiple tables, it's slow using ODBC conections. Either you have to use those queries in the SQL Server view or you have...