[mapguide-users] RE: ODBC Provider with SQL Server 2005: Does it worksfor somebody?

[FGoulet]

Sure,

Here's the script:

USE [DredgingRegister]
GO
/****** Object:  Table [dbo].[Dredging_Activity]    Script Date: 01/31/2007
14:53:46 ******/
SET ANSI_NULLS ON
GO
SET QUOTED_IDENTIFIER ON
GO
CREATE TABLE [dbo].[Dredging_Activity](
	[Activity_ID] [int] IDENTITY(1,1) NOT NULL,
	[UserName] [nvarchar](256) COLLATE SQL_Latin1_General_CP1_CI_AS NULL,
	[Location_FR] [nvarchar](32) COLLATE SQL_Latin1_General_CP1_CI_AS NULL,
	[Location_EN] [nvarchar](32) COLLATE SQL_Latin1_General_CP1_CI_AS NULL,
	[Description_FR] [nvarchar](32) COLLATE SQL_Latin1_General_CP1_CI_AS NULL,
	[Description_EN] [nvarchar](32) COLLATE SQL_Latin1_General_CP1_CI_AS NULL,
	[Start_Date] [datetime] NULL,
	[Finish_Date] [datetime] NULL,
	[Dredging_Type_CD] [int] NULL,
	[Material_Quantity] [numeric](9, 3) NULL,
	[Material_Disposal] [nchar](10) COLLATE SQL_Latin1_General_CP1_CI_AS NULL,
	[Longitude] [float] NULL,
	[Latitude] [float] NULL,
	[Registration_Date] [datetime] NULL,
	[Approved] [bit] NULL,
	[Proponent_ID] [int] NULL,
	[Responsible_ID] [int] NULL,
 CONSTRAINT [PK_Dredging_Activity] PRIMARY KEY CLUSTERED 
(
	[Activity_ID] ASC
)WITH (PAD_INDEX  = OFF, IGNORE_DUP_KEY = OFF) ON [PRIMARY]
) ON [PRIMARY]

GO
ALTER TABLE [dbo].[Dredging_Activity]  WITH CHECK ADD  CONSTRAINT
[FK_Dredging_Activity_Contact] FOREIGN KEY([Responsible_ID])
REFERENCES [dbo].[Contact] ([Contact_ID])
GO
ALTER TABLE [dbo].[Dredging_Activity] CHECK CONSTRAINT
[FK_Dredging_Activity_Contact]
GO
ALTER TABLE [dbo].[Dredging_Activity]  WITH CHECK ADD  CONSTRAINT
[FK_Dredging_Activity_Dredging_Type] FOREIGN KEY([Dredging_Type_CD])
REFERENCES [dbo].[Dredging_Type] ([Dredging_Type_CD])
GO
ALTER TABLE [dbo].[Dredging_Activity] CHECK CONSTRAINT
[FK_Dredging_Activity_Dredging_Type]
GO
ALTER TABLE [dbo].[Dredging_Activity]  WITH CHECK ADD  CONSTRAINT
[FK_Dredging_Activity_Proponent] FOREIGN KEY([Proponent_ID])
REFERENCES [dbo].[Proponent] ([Proponent_ID])
GO
ALTER TABLE [dbo].[Dredging_Activity] CHECK CONSTRAINT
[FK_Dredging_Activity_Proponent]


The columns mapped to X and Y in MG Studio are Longitude and Latitude. I
tried with  others numeric type (real, decimal, numeric) and I always get
that error.


Thanks




JasonBirch wrote:
> 
> Frederic wrote:
>  
>         An exception occurred in FDO component.
>         RDBMS: Incompatible column type
> 
> Care to share the table definition?  The problem with ODBC is that it's
> not generic enough :)
>  
> Jason
>  
> 
>  
> _______________________________________________
> mapguide-users mailing list
> mapguide-users at lists.osgeo.org
> http://lists.osgeo.org/mailman/listinfo/mapguide-users
> 
> 

-- 
View this message in context: http://www.nabble.com/ODBC-Provider-with-SQL-Server-2005%3A-Does-it-works-for-somebody--tf3144880s16610.html#a8806498
Sent from the MapGuide Users mailing list archive at Nabble.com.