 |
BorlandTalk.com Borland discussion newsgroups
|
| View previous topic :: View next topic |
| Author |
Message |
Kevin Willems Guest
|
Posted: Tue Aug 12, 2003 9:06 pm Post subject: Fields added when setting up replication |
|
|
Hi all,
I am trying to set up Merge replication on SQL Server 2000. I used the
wizard. It added a field to the end of each of the tables that I wanted to
publish called RowGuid of type UniqueIdentifier. Now when my application
tries to open these tables I get the error message:
General SQL Error
[Microsoft][ODBC SQL Server] Numeric value out of range
Does anyone know how to prevent this?
Thanks,
Kevin Willems
|
|
| Back to top |
|
 |
Kevin Frevert Guest
|
Posted: Wed Aug 13, 2003 4:26 pm Post subject: Re: Fields added when setting up replication |
|
|
Kevin,
What data-access components (TTables, TQuerys, TADOx, etc) are you using?
krf
"Kevin Willems" <info (AT) kdwillems (DOT) com> wrote
| Quote: | Hi all,
I am trying to set up Merge replication on SQL Server 2000. I used the
wizard. It added a field to the end of each of the tables that I wanted to
publish called RowGuid of type UniqueIdentifier. Now when my application
tries to open these tables I get the error message:
General SQL Error
[Microsoft][ODBC SQL Server] Numeric value out of range
Does anyone know how to prevent this?
Thanks,
Kevin Willems
|
|
|
| Back to top |
|
 |
Kevin Willems Guest
|
Posted: Mon Aug 18, 2003 7:51 pm Post subject: Re: Fields added when setting up replication |
|
|
Thanks for the info!!!
Kevin Willems
"Kevin Frevert" <kevin (AT) workdrinkingcoffee (DOT) com> wrote
| Quote: | Kevin,
The BDE (and Microsoft's DBLib) has been depreciated and may not fully
support the new datatypes introduced in MSSQL 7.0.
http://support.microsoft.com/default.aspx?scid=kb;en-us;260817
Other articals of interest.
http://community.borland.com/article/0,1410,28688,00.html
http://community.borland.com/article/0,1410,10359,00.html
http://community.borland.com/article/0,1410,19694,00.html
Microsoft's/Borland's solution is to use ADO (OLE-DB). If that is not
feasible at this time, you could cast that field like...
Select CAST(MyUniqueIdentifierField as varchar) [MyUniqueIdentifierField]
Good luck,
krf
"Kevin Willems" <info (AT) kdwillems (DOT) com> wrote in message
news:3f3bfb00$1 (AT) newsgroups (DOT) borland.com...
What data-access components (TTables, TQuerys, TADOx, etc) are you
using?
I am using TTables and TQueries. These go through the BDE to SQL Server
via
the SQL Server ODBC driver.
I have now discovered that the BDE does not know how to deal with the
UniqueIdentifier type. My application does not use this field at all,
but
I
do make use of SELECT * statements. Is there any way of translating this
field type before it gets to the BDE? Otherwise I won't be able to use
replication, which is too bad because it looks like it would simplify my
life enormously.
Thanks,
Kevin Willems
|
|
|
| Back to top |
|
 |
|
|
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum
|
|