Sybase ODBC - Reserved Error (-7748); there is no Message on this error

Author

Reserved Error (-7748); there is no Message on this error

Somen Pal

2005-06-07, 11:23 am

Hallo Group,

I connect tables from MS access 2002 running on
my windows XP PC to my Sybase ASE 12.5 Server. The ODBC
driver is named "Sybase ASE ODBC driver" version
"5.00.00.56"

I get a connection to the database but if I choose a table
I get the error:
"Reserved Error (-7748); there is no Message on this error".

I fixed the error by following solution.

1. Bring up regedit
2. Go to the following directory:
HKEY_LOCAL_MACHINE -> Software -> ODBC -> ODBC.INI ->
your_DSN_name
3. Select your data source and chose "edit" -> "New" ->
"string value"
from the menu (for more information, see "More Details",
below)
4. Change the name of the new string value to read
"WorkArounds2"
5. Double click on "WorkArounds2" in the right hand panel
and bring up a box with data value
6. Change data value to 8192

I found the fix is working without modifying the DSN
definition on user machines. I would like to know the ripple
effects of the solution (if Any.

Thanks,
Somen.

Paul

2005-06-07, 11:23 am

Hi Somen,

Don't know of side effects. This is the solution to the ms access problem.
Apparently it is coded this way so as to not affect other uses of a Data
Source with apps like VB/ADO, etc.

-pv

<Somen Pal> wrote in message news:42a5c074.3206.1681692777@sybase.com...
> Hallo Group,
>
> I connect tables from MS access 2002 running on
> my windows XP PC to my Sybase ASE 12.5 Server. The ODBC
> driver is named "Sybase ASE ODBC driver" version
> "5.00.00.56"
>
> I get a connection to the database but if I choose a table
> I get the error:
> "Reserved Error (-7748); there is no Message on this error".
>
> I fixed the error by following solution.
>
> 1. Bring up regedit
> 2. Go to the following directory:
> HKEY_LOCAL_MACHINE -> Software -> ODBC -> ODBC.INI ->
> your_DSN_name
> 3. Select your data source and chose "edit" -> "New" ->
> "string value"
> from the menu (for more information, see "More Details",
> below)
> 4. Change the name of the new string value to read
> "WorkArounds2"
> 5. Double click on "WorkArounds2" in the right hand panel
> and bring up a box with data value
> 6. Change data value to 8192
>
> I found the fix is working without modifying the DSN
> definition on user machines. I would like to know the ripple
> effects of the solution (if Any.
>
> Thanks,
> Somen.

Sponsored Links