Showing posts with label format. Show all posts
Showing posts with label format. Show all posts

Monday, March 26, 2012

Question regarding connections with MSAccess

I have a Access 2002 (saved as 2K format) front end to a SQL Server (2000 I believe) and everything worked fine until I added 30 new fields to the main table. All of these fields are data type Bit and all are initialized to zero. I can add new records without any issues. The problem is that any time I try to update or delete a record I get the dreaded "Write Conflict..." msg in Access. If I use an older version of the system without refreshing the linked tables I have no problems. This behavior is also exhibited if I try to update/delete a record directly in the table so I know it is not something in my forms. Any help would be greatly appreciated.

Ron

The solution was to change the data type on the SQL Server to a 1 byte text field and poputate it programatically rather then having it directly bound to a control such as a checkbox. I never got a good answer as to why this was happening so I had to use the previously described workaround.

Question regarding connections with MSAccess

I have a Access 2002 (saved as 2K format) front end to a SQL Server (2000 I believe) and everything worked fine until I added 30 new fields to the main table. All of these fields are data type Bit and all are initialized to zero. I can add new records without any issues. The problem is that any time I try to update or delete a record I get the dreaded "Write Conflict..." msg in Access. If I use an older version of the system without refreshing the linked tables I have no problems. This behavior is also exhibited if I try to update/delete a record directly in the table so I know it is not something in my forms. Any help would be greatly appreciated.

Ron

The solution was to change the data type on the SQL Server to a 1 byte text field and poputate it programatically rather then having it directly bound to a control such as a checkbox. I never got a good answer as to why this was happening so I had to use the previously described workaround.sql

Monday, March 12, 2012

question on ntext datatype in sql server

What is the max. number of characters in ntext?

Are there any way we can format the output of ntext? Or it will just come out as one long line?

Thanks.

Its just data of the following definition:

ntext

Variable-length Unicode data with a maximum length of 2^30 - 1 (1,073,741,823) characters. Storage size, in bytes, is two times the number of characters entered. The SQL-2003 synonym for ntext is national text.

formatting is up to you after retrieving it from the database.

HTH, jens Suessmeyer.

http://www.sqlserver2005.de