T
teddysnips
I have recently upsized a client database to SQL Server.
The application is used to book people onto courses at a Conference
Centre/Adult Study Centre.
It was originally an Access FE/BE, all written by my client. While
it's not bad as an "amateur" database, it has all the expected
failings of the inexperienced developer (poor table design, queries
operating on whole tables, macros running hither and yon mixed with
code etc.)
The FE resides on a server, and all users (about four or five at most)
connect to it. The BE resides on a different server.
Recently, the users have been getting intermittent ODBC error messages
- mostly 3146 ODBC Call Failed, but also
ODBC Call Failed
[Microsoft][ODBC Driver Manager] Invalid Argument Value (#0)
What makes this very difficult to diagnose is that the errors are not
persistent. Yesterday, for example, certain processes threw 3146
errors constantly. Today, the same processes run without problems.
What I would REALLY like to do is to rationalise/normalise the data
design, move ALL the macros to code and redesign all the queries.
Sadly their budget is very limited.
Does anyone have any ideas about how to resolve the immediate,
intermittent problem?
Many thanks
Edward
The application is used to book people onto courses at a Conference
Centre/Adult Study Centre.
It was originally an Access FE/BE, all written by my client. While
it's not bad as an "amateur" database, it has all the expected
failings of the inexperienced developer (poor table design, queries
operating on whole tables, macros running hither and yon mixed with
code etc.)
The FE resides on a server, and all users (about four or five at most)
connect to it. The BE resides on a different server.
Recently, the users have been getting intermittent ODBC error messages
- mostly 3146 ODBC Call Failed, but also
ODBC Call Failed
[Microsoft][ODBC Driver Manager] Invalid Argument Value (#0)
What makes this very difficult to diagnose is that the errors are not
persistent. Yesterday, for example, certain processes threw 3146
errors constantly. Today, the same processes run without problems.
What I would REALLY like to do is to rationalise/normalise the data
design, move ALL the macros to code and redesign all the queries.
Sadly their budget is very limited.
Does anyone have any ideas about how to resolve the immediate,
intermittent problem?
Many thanks
Edward