I've got a SQL table that I created through the Access 2K2 interface that is
suddenly giving me a warning message each time I attempt to open the table
in design mode or datasheet mode which says:
"The setting for the DecimalPlaces property must be from 0 through 15, or 25
5 for Auto (default)."
I have checked, rechecked, and checked again the format for every item in my
table, and none of them have a DecimalPlaces property outside of this range
. In fact, only three smallmoney fields have any DecimalPlaces setting at al
l - each is 0. The rest of
the numeric fields are all specified as General Number, and the Decimal Plac
es property is blank (and inaccessible). I have been completely unable to fi
nd any information on this on SQL Server BOL, the KB or these newsgroups. Ha
s anyone else encountered t
his behavior? Any idea why it may be occurring, and what I can do to stop it
? BTW, this is a new table with no data, and the warning message only recent
ly started appearing - it didn't always do so.
TIA,
Terry Roberts>
> I've got a SQL table that I created through the Access 2K2
> interface that is suddenly giving me a warning message each time
> I attempt to open the table in design mode or datasheet mode
> which says:
> "The setting for the DecimalPlaces property must be from 0
> through 15, or 255 for Auto (default)."
--
Hi Terry,
Try deleting the linked table in Access and relink. See if the problem goes
away.
If the problem persists, post your question in one of the Microsoft Access
forums and someone might be able to help.
Hope this helps,
Eric Crdenas
Senior support professional
This posting is provided "AS IS" with no warranties, and confers no rights.|||Eric,
Thanks for the advice - unfortunately, it didn't solve the problem. I'll try
a post to the Access newsgroup.
Terry
Showing posts with label interface. Show all posts
Showing posts with label interface. Show all posts
Friday, March 9, 2012
DecimalPlaces Property
I've got a SQL table that I created through the Access 2K2 interface that is suddenly giving me a warning message each time I attempt to open the table in design mode or datasheet mode which says:
"The setting for the DecimalPlaces property must be from 0 through 15, or 255 for Auto (default)."
I have checked, rechecked, and checked again the format for every item in my table, and none of them have a DecimalPlaces property outside of this range. In fact, only three smallmoney fields have any DecimalPlaces setting at all - each is 0. The rest of
the numeric fields are all specified as General Number, and the Decimal Places property is blank (and inaccessible). I have been completely unable to find any information on this on SQL Server BOL, the KB or these newsgroups. Has anyone else encountered t
his behavior? Any idea why it may be occurring, and what I can do to stop it? BTW, this is a new table with no data, and the warning message only recently started appearing - it didn't always do so.
TIA,
Terry Roberts
>
> I've got a SQL table that I created through the Access 2K2
> interface that is suddenly giving me a warning message each time
> I attempt to open the table in design mode or datasheet mode
> which says:
> "The setting for the DecimalPlaces property must be from 0
> through 15, or 255 for Auto (default)."
Hi Terry,
Try deleting the linked table in Access and relink. See if the problem goes
away.
If the problem persists, post your question in one of the Microsoft Access
forums and someone might be able to help.
Hope this helps,
Eric Crdenas
Senior support professional
This posting is provided "AS IS" with no warranties, and confers no rights.
|||Eric,
Thanks for the advice - unfortunately, it didn't solve the problem. I'll try a post to the Access newsgroup.
Terry
"The setting for the DecimalPlaces property must be from 0 through 15, or 255 for Auto (default)."
I have checked, rechecked, and checked again the format for every item in my table, and none of them have a DecimalPlaces property outside of this range. In fact, only three smallmoney fields have any DecimalPlaces setting at all - each is 0. The rest of
the numeric fields are all specified as General Number, and the Decimal Places property is blank (and inaccessible). I have been completely unable to find any information on this on SQL Server BOL, the KB or these newsgroups. Has anyone else encountered t
his behavior? Any idea why it may be occurring, and what I can do to stop it? BTW, this is a new table with no data, and the warning message only recently started appearing - it didn't always do so.
TIA,
Terry Roberts
>
> I've got a SQL table that I created through the Access 2K2
> interface that is suddenly giving me a warning message each time
> I attempt to open the table in design mode or datasheet mode
> which says:
> "The setting for the DecimalPlaces property must be from 0
> through 15, or 255 for Auto (default)."
Hi Terry,
Try deleting the linked table in Access and relink. See if the problem goes
away.
If the problem persists, post your question in one of the Microsoft Access
forums and someone might be able to help.
Hope this helps,
Eric Crdenas
Senior support professional
This posting is provided "AS IS" with no warranties, and confers no rights.
|||Eric,
Thanks for the advice - unfortunately, it didn't solve the problem. I'll try a post to the Access newsgroup.
Terry
DecimalPlaces Property
I've got a SQL table that I created through the Access 2K2 interface that is suddenly giving me a warning message each time I attempt to open the table in design mode or datasheet mode which says
"The setting for the DecimalPlaces property must be from 0 through 15, or 255 for Auto (default).
I have checked, rechecked, and checked again the format for every item in my table, and none of them have a DecimalPlaces property outside of this range. In fact, only three smallmoney fields have any DecimalPlaces setting at all - each is 0. The rest of the numeric fields are all specified as General Number, and the Decimal Places property is blank (and inaccessible). I have been completely unable to find any information on this on SQL Server BOL, the KB or these newsgroups. Has anyone else encountered this behavior? Any idea why it may be occurring, and what I can do to stop it? BTW, this is a new table with no data, and the warning message only recently started appearing - it didn't always do so
TIA
Terry Roberts>
> I've got a SQL table that I created through the Access 2K2
> interface that is suddenly giving me a warning message each time
> I attempt to open the table in design mode or datasheet mode
> which says:
> "The setting for the DecimalPlaces property must be from 0
> through 15, or 255 for Auto (default)."
--
Hi Terry,
Try deleting the linked table in Access and relink. See if the problem goes
away.
If the problem persists, post your question in one of the Microsoft Access
forums and someone might be able to help.
Hope this helps,
--
Eric Cárdenas
Senior support professional
This posting is provided "AS IS" with no warranties, and confers no rights.|||Eric
Thanks for the advice - unfortunately, it didn't solve the problem. I'll try a post to the Access newsgroup
Terry
"The setting for the DecimalPlaces property must be from 0 through 15, or 255 for Auto (default).
I have checked, rechecked, and checked again the format for every item in my table, and none of them have a DecimalPlaces property outside of this range. In fact, only three smallmoney fields have any DecimalPlaces setting at all - each is 0. The rest of the numeric fields are all specified as General Number, and the Decimal Places property is blank (and inaccessible). I have been completely unable to find any information on this on SQL Server BOL, the KB or these newsgroups. Has anyone else encountered this behavior? Any idea why it may be occurring, and what I can do to stop it? BTW, this is a new table with no data, and the warning message only recently started appearing - it didn't always do so
TIA
Terry Roberts>
> I've got a SQL table that I created through the Access 2K2
> interface that is suddenly giving me a warning message each time
> I attempt to open the table in design mode or datasheet mode
> which says:
> "The setting for the DecimalPlaces property must be from 0
> through 15, or 255 for Auto (default)."
--
Hi Terry,
Try deleting the linked table in Access and relink. See if the problem goes
away.
If the problem persists, post your question in one of the Microsoft Access
forums and someone might be able to help.
Hope this helps,
--
Eric Cárdenas
Senior support professional
This posting is provided "AS IS" with no warranties, and confers no rights.|||Eric
Thanks for the advice - unfortunately, it didn't solve the problem. I'll try a post to the Access newsgroup
Terry
Friday, February 17, 2012
Debugger Interface Problem in QA
Hello,
We've setup SQL Debugging on our server, but when I try and test in Query
Analyzer on the server I get the following error:
"The debugger interface is not installed. Please re-run setup, select "add
components to your existing installation' and make sure you select
'Development tools'\'Debugger Interface'."
However, this is already installed when I run setup. I am running SQL SP3,
and noticed some articles about that, but they didn't seem to apply to my
specific problem. I get the same error whether through terminal services or
at the console.
We're having a lot of problems making this work, if anyone can assist I'd
greatly appreciate.
Regards,
Derek
I'm seeing the same issue, did you ever get a resolution?
Ron
"Derek" wrote:
> Hello,
> We've setup SQL Debugging on our server, but when I try and test in Query
> Analyzer on the server I get the following error:
> "The debugger interface is not installed. Please re-run setup, select "add
> components to your existing installation' and make sure you select
> 'Development tools'\'Debugger Interface'."
> However, this is already installed when I run setup. I am running SQL SP3,
> and noticed some articles about that, but they didn't seem to apply to my
> specific problem. I get the same error whether through terminal services or
> at the console.
> We're having a lot of problems making this work, if anyone can assist I'd
> greatly appreciate.
> Regards,
> Derek
>
>
We've setup SQL Debugging on our server, but when I try and test in Query
Analyzer on the server I get the following error:
"The debugger interface is not installed. Please re-run setup, select "add
components to your existing installation' and make sure you select
'Development tools'\'Debugger Interface'."
However, this is already installed when I run setup. I am running SQL SP3,
and noticed some articles about that, but they didn't seem to apply to my
specific problem. I get the same error whether through terminal services or
at the console.
We're having a lot of problems making this work, if anyone can assist I'd
greatly appreciate.
Regards,
Derek
I'm seeing the same issue, did you ever get a resolution?
Ron
"Derek" wrote:
> Hello,
> We've setup SQL Debugging on our server, but when I try and test in Query
> Analyzer on the server I get the following error:
> "The debugger interface is not installed. Please re-run setup, select "add
> components to your existing installation' and make sure you select
> 'Development tools'\'Debugger Interface'."
> However, this is already installed when I run setup. I am running SQL SP3,
> and noticed some articles about that, but they didn't seem to apply to my
> specific problem. I get the same error whether through terminal services or
> at the console.
> We're having a lot of problems making this work, if anyone can assist I'd
> greatly appreciate.
> Regards,
> Derek
>
>
Debugger Interface Problem in QA
Hello,
We've setup SQL Debugging on our server, but when I try and test in Query
Analyzer on the server I get the following error:
"The debugger interface is not installed. Please re-run setup, select "add
components to your existing installation' and make sure you select
'Development tools'\'Debugger Interface'."
However, this is already installed when I run setup. I am running SQL SP3,
and noticed some articles about that, but they didn't seem to apply to my
specific problem. I get the same error whether through terminal services or
at the console.
We're having a lot of problems making this work, if anyone can assist I'd
greatly appreciate.
Regards,
DerekI'm seeing the same issue, did you ever get a resolution?
Ron
"Derek" wrote:
> Hello,
> We've setup SQL Debugging on our server, but when I try and test in Query
> Analyzer on the server I get the following error:
> "The debugger interface is not installed. Please re-run setup, select "add
> components to your existing installation' and make sure you select
> 'Development tools'\'Debugger Interface'."
> However, this is already installed when I run setup. I am running SQL SP3,
> and noticed some articles about that, but they didn't seem to apply to my
> specific problem. I get the same error whether through terminal services or
> at the console.
> We're having a lot of problems making this work, if anyone can assist I'd
> greatly appreciate.
> Regards,
> Derek
>
>
We've setup SQL Debugging on our server, but when I try and test in Query
Analyzer on the server I get the following error:
"The debugger interface is not installed. Please re-run setup, select "add
components to your existing installation' and make sure you select
'Development tools'\'Debugger Interface'."
However, this is already installed when I run setup. I am running SQL SP3,
and noticed some articles about that, but they didn't seem to apply to my
specific problem. I get the same error whether through terminal services or
at the console.
We're having a lot of problems making this work, if anyone can assist I'd
greatly appreciate.
Regards,
DerekI'm seeing the same issue, did you ever get a resolution?
Ron
"Derek" wrote:
> Hello,
> We've setup SQL Debugging on our server, but when I try and test in Query
> Analyzer on the server I get the following error:
> "The debugger interface is not installed. Please re-run setup, select "add
> components to your existing installation' and make sure you select
> 'Development tools'\'Debugger Interface'."
> However, this is already installed when I run setup. I am running SQL SP3,
> and noticed some articles about that, but they didn't seem to apply to my
> specific problem. I get the same error whether through terminal services or
> at the console.
> We're having a lot of problems making this work, if anyone can assist I'd
> greatly appreciate.
> Regards,
> Derek
>
>
debugger interface
Help,
I used to be able to debug a stored procedure in the query analyser.
But now I get an error indicating that I should re-run setup and add the
debugger interface.
the debugger is installed!!!!
if I take a look at the eventviewer I see following error
DCOM got error "the operation completed successfully" and was unable to
togon , \SQLdebugger in order to run the server.
What can I do to correct this problem and switch debugging on again?
Thanks,
MarcIt sounds like the DCOM permissions may no longer set
correctly. Check the topic in books online: Troubleshooting
the Transact-SQL Debugger
Make sure you follow all the steps, especially those for
DCOMCNFG.EXE
You should also check the following knowledge base article:
INF: T-SQL Debugger Is Turned Off By Default for Earlier
Clients After You Install SQL Server 2000 Service Pack 3
http://support.microsoft.com/?id=328151
-Sue
On Tue, 12 Apr 2005 09:40:48 +0200, "marc" <heev@.msn.com>
wrote:
>Help,
>I used to be able to debug a stored procedure in the query analyser.
>But now I get an error indicating that I should re-run setup and add the
>debugger interface.
>the debugger is installed!!!!
>if I take a look at the eventviewer I see following error
>DCOM got error "the operation completed successfully" and was unable to
>togon , \SQLdebugger in order to run the server.
>What can I do to correct this problem and switch debugging on again?
>Thanks,
>Marc
>
I used to be able to debug a stored procedure in the query analyser.
But now I get an error indicating that I should re-run setup and add the
debugger interface.
the debugger is installed!!!!
if I take a look at the eventviewer I see following error
DCOM got error "the operation completed successfully" and was unable to
togon , \SQLdebugger in order to run the server.
What can I do to correct this problem and switch debugging on again?
Thanks,
MarcIt sounds like the DCOM permissions may no longer set
correctly. Check the topic in books online: Troubleshooting
the Transact-SQL Debugger
Make sure you follow all the steps, especially those for
DCOMCNFG.EXE
You should also check the following knowledge base article:
INF: T-SQL Debugger Is Turned Off By Default for Earlier
Clients After You Install SQL Server 2000 Service Pack 3
http://support.microsoft.com/?id=328151
-Sue
On Tue, 12 Apr 2005 09:40:48 +0200, "marc" <heev@.msn.com>
wrote:
>Help,
>I used to be able to debug a stored procedure in the query analyser.
>But now I get an error indicating that I should re-run setup and add the
>debugger interface.
>the debugger is installed!!!!
>if I take a look at the eventviewer I see following error
>DCOM got error "the operation completed successfully" and was unable to
>togon , \SQLdebugger in order to run the server.
>What can I do to correct this problem and switch debugging on again?
>Thanks,
>Marc
>
debugger interface
Help,
I used to be able to debug a stored procedure in the query analyser.
But now I get an error indicating that I should re-run setup and add the
debugger interface.
the debugger is installed!!!!
if I take a look at the eventviewer I see following error
DCOM got error "the operation completed successfully" and was unable to
togon , \SQLdebugger in order to run the server.
What can I do to correct this problem and switch debugging on again?
Thanks,
MarcIt sounds like the DCOM permissions may no longer set
correctly. Check the topic in books online: Troubleshooting
the Transact-SQL Debugger
Make sure you follow all the steps, especially those for
DCOMCNFG.EXE
You should also check the following knowledge base article:
INF: T-SQL Debugger Is Turned Off By Default for Earlier
Clients After You Install SQL Server 2000 Service Pack 3
http://support.microsoft.com/?id=328151
-Sue
On Tue, 12 Apr 2005 09:40:48 +0200, "marc" <heev@.msn.com>
wrote:
>Help,
>I used to be able to debug a stored procedure in the query analyser.
>But now I get an error indicating that I should re-run setup and add the
>debugger interface.
>the debugger is installed!!!!
>if I take a look at the eventviewer I see following error
>DCOM got error "the operation completed successfully" and was unable to
>togon , \SQLdebugger in order to run the server.
>What can I do to correct this problem and switch debugging on again?
>Thanks,
>Marc
>
I used to be able to debug a stored procedure in the query analyser.
But now I get an error indicating that I should re-run setup and add the
debugger interface.
the debugger is installed!!!!
if I take a look at the eventviewer I see following error
DCOM got error "the operation completed successfully" and was unable to
togon , \SQLdebugger in order to run the server.
What can I do to correct this problem and switch debugging on again?
Thanks,
MarcIt sounds like the DCOM permissions may no longer set
correctly. Check the topic in books online: Troubleshooting
the Transact-SQL Debugger
Make sure you follow all the steps, especially those for
DCOMCNFG.EXE
You should also check the following knowledge base article:
INF: T-SQL Debugger Is Turned Off By Default for Earlier
Clients After You Install SQL Server 2000 Service Pack 3
http://support.microsoft.com/?id=328151
-Sue
On Tue, 12 Apr 2005 09:40:48 +0200, "marc" <heev@.msn.com>
wrote:
>Help,
>I used to be able to debug a stored procedure in the query analyser.
>But now I get an error indicating that I should re-run setup and add the
>debugger interface.
>the debugger is installed!!!!
>if I take a look at the eventviewer I see following error
>DCOM got error "the operation completed successfully" and was unable to
>togon , \SQLdebugger in order to run the server.
>What can I do to correct this problem and switch debugging on again?
>Thanks,
>Marc
>
debugger interface
Help,
I used to be able to debug a stored procedure in the query analyser.
But now I get an error indicating that I should re-run setup and add the
debugger interface.
the debugger is installed!!!!
if I take a look at the eventviewer I see following error
DCOM got error "the operation completed successfully" and was unable to
togon , \SQLdebugger in order to run the server.
What can I do to correct this problem and switch debugging on again?
Thanks,
MarcIt sounds like the DCOM permissions may no longer set
correctly. Check the topic in books online: Troubleshooting
the Transact-SQL Debugger
Make sure you follow all the steps, especially those for
DCOMCNFG.EXE
You should also check the following knowledge base article:
INF: T-SQL Debugger Is Turned Off By Default for Earlier
Clients After You Install SQL Server 2000 Service Pack 3
http://support.microsoft.com/?id=328151
-Sue
On Tue, 12 Apr 2005 09:40:48 +0200, "marc" <heev@.msn.com>
wrote:
>Help,
>I used to be able to debug a stored procedure in the query analyser.
>But now I get an error indicating that I should re-run setup and add the
>debugger interface.
>the debugger is installed!!!!
>if I take a look at the eventviewer I see following error
>DCOM got error "the operation completed successfully" and was unable to
>togon , \SQLdebugger in order to run the server.
>What can I do to correct this problem and switch debugging on again?
>Thanks,
>Marc
>
I used to be able to debug a stored procedure in the query analyser.
But now I get an error indicating that I should re-run setup and add the
debugger interface.
the debugger is installed!!!!
if I take a look at the eventviewer I see following error
DCOM got error "the operation completed successfully" and was unable to
togon , \SQLdebugger in order to run the server.
What can I do to correct this problem and switch debugging on again?
Thanks,
MarcIt sounds like the DCOM permissions may no longer set
correctly. Check the topic in books online: Troubleshooting
the Transact-SQL Debugger
Make sure you follow all the steps, especially those for
DCOMCNFG.EXE
You should also check the following knowledge base article:
INF: T-SQL Debugger Is Turned Off By Default for Earlier
Clients After You Install SQL Server 2000 Service Pack 3
http://support.microsoft.com/?id=328151
-Sue
On Tue, 12 Apr 2005 09:40:48 +0200, "marc" <heev@.msn.com>
wrote:
>Help,
>I used to be able to debug a stored procedure in the query analyser.
>But now I get an error indicating that I should re-run setup and add the
>debugger interface.
>the debugger is installed!!!!
>if I take a look at the eventviewer I see following error
>DCOM got error "the operation completed successfully" and was unable to
>togon , \SQLdebugger in order to run the server.
>What can I do to correct this problem and switch debugging on again?
>Thanks,
>Marc
>
debugger interface
Help,
I used to be able to debug a stored procedure in the query analyser.
But now I get an error indicating that I should re-run setup and add the
debugger interface.
the debugger is installed!!!!
if I take a look at the eventviewer I see following error
DCOM got error "the operation completed successfully" and was unable to
togon , \SQLdebugger in order to run the server.
What can I do to correct this problem and switch debugging on again?
Thanks,
Marc
It sounds like the DCOM permissions may no longer set
correctly. Check the topic in books online: Troubleshooting
the Transact-SQL Debugger
Make sure you follow all the steps, especially those for
DCOMCNFG.EXE
You should also check the following knowledge base article:
INF: T-SQL Debugger Is Turned Off By Default for Earlier
Clients After You Install SQL Server 2000 Service Pack 3
http://support.microsoft.com/?id=328151
-Sue
On Tue, 12 Apr 2005 09:40:48 +0200, "marc" <heev@.msn.com>
wrote:
>Help,
>I used to be able to debug a stored procedure in the query analyser.
>But now I get an error indicating that I should re-run setup and add the
>debugger interface.
>the debugger is installed!!!!
>if I take a look at the eventviewer I see following error
>DCOM got error "the operation completed successfully" and was unable to
>togon , \SQLdebugger in order to run the server.
>What can I do to correct this problem and switch debugging on again?
>Thanks,
>Marc
>
I used to be able to debug a stored procedure in the query analyser.
But now I get an error indicating that I should re-run setup and add the
debugger interface.
the debugger is installed!!!!
if I take a look at the eventviewer I see following error
DCOM got error "the operation completed successfully" and was unable to
togon , \SQLdebugger in order to run the server.
What can I do to correct this problem and switch debugging on again?
Thanks,
Marc
It sounds like the DCOM permissions may no longer set
correctly. Check the topic in books online: Troubleshooting
the Transact-SQL Debugger
Make sure you follow all the steps, especially those for
DCOMCNFG.EXE
You should also check the following knowledge base article:
INF: T-SQL Debugger Is Turned Off By Default for Earlier
Clients After You Install SQL Server 2000 Service Pack 3
http://support.microsoft.com/?id=328151
-Sue
On Tue, 12 Apr 2005 09:40:48 +0200, "marc" <heev@.msn.com>
wrote:
>Help,
>I used to be able to debug a stored procedure in the query analyser.
>But now I get an error indicating that I should re-run setup and add the
>debugger interface.
>the debugger is installed!!!!
>if I take a look at the eventviewer I see following error
>DCOM got error "the operation completed successfully" and was unable to
>togon , \SQLdebugger in order to run the server.
>What can I do to correct this problem and switch debugging on again?
>Thanks,
>Marc
>
Subscribe to:
Posts (Atom)