Group:  Microsoft Access ยป microsoft.public.access.adp.sqlserver
Thread: Lookup Columns in ADP/SQL Server 2005 combination

DotNetBag
.NET Development Newsgroups

HTVi
TV Discussion Newsgroups

Our Hot Pick: Rising Antivirus 2006 - Certified by TUV & Checkmark! Get 10% discount by entering this coupon code: ONDISCOUNT10
Rising Antivirus 2006

Lookup Columns in ADP/SQL Server 2005 combination
"MarkEJackson" <mjackson11[ at ]houston.rr.com> 21.09.2006 19:52:23
I have an ADP that was linked to SQL2K, now to SQL2005. There are
tables that contain lookup columns (the data was an integer link to a
record in another table) that displayed values in easy to read formats.
The columns that were created in SQL2K still work and have the lookup
information. New columns that are created since the conversion cannot
be changed to lookup columns. Is there a way around this as the lookup
data has to be local to Access's ADP file?

Thx

Mark Jackson

Re: Lookup Columns in ADP/SQL Server 2005 combination
"Sylvain Lafontaine" <sylvain aei ca (fill the blanks, no spam please)> 21.09.2006 20:45:14
The lookup properties are stored as extended properties on the SQL-Server
side. Maybe you can manage yourself these properties as required by ADP.
If you want to take a look at these properties:

http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnsqlpro02/html/sql02a10.asp

--
Sylvain Lafontaine, ing.
MVP - Technologies Virtual-PC
E-mail: http://cerbermail.com/?QugbLEWINF


"MarkEJackson" <mjackson11[ at ]houston.rr.com> wrote in message
news:1158868342.969012.83840[ at ]d34g2000cwd.googlegroups.com...
[Quoted Text]
>I have an ADP that was linked to SQL2K, now to SQL2005. There are
> tables that contain lookup columns (the data was an integer link to a
> record in another table) that displayed values in easy to read formats.
> The columns that were created in SQL2K still work and have the lookup
> information. New columns that are created since the conversion cannot
> be changed to lookup columns. Is there a way around this as the lookup
> data has to be local to Access's ADP file?
>
> Thx
>
> Mark Jackson
>


Re: Lookup Columns in ADP/SQL Server 2005 combination
"Sylvain Lafontaine" <sylvain aei ca (fill the blanks, no spam please)> 21.09.2006 20:46:59
However, the best solution would be to design and use a form instead of a
datasheet. With a form, you have full control on everything.

--
Sylvain Lafontaine, ing.
MVP - Technologies Virtual-PC
E-mail: http://cerbermail.com/?QugbLEWINF


"MarkEJackson" <mjackson11[ at ]houston.rr.com> wrote in message
news:1158868342.969012.83840[ at ]d34g2000cwd.googlegroups.com...
[Quoted Text]
>I have an ADP that was linked to SQL2K, now to SQL2005. There are
> tables that contain lookup columns (the data was an integer link to a
> record in another table) that displayed values in easy to read formats.
> The columns that were created in SQL2K still work and have the lookup
> information. New columns that are created since the conversion cannot
> be changed to lookup columns. Is there a way around this as the lookup
> data has to be local to Access's ADP file?
>
> Thx
>
> Mark Jackson
>


Re: Lookup Columns in ADP/SQL Server 2005 combination
"MarkEJackson" <mjackson11[ at ]houston.rr.com> 21.09.2006 20:54:14
As soon as I posted, found my own answer, the lookup info is stored on
the SQL server as an extended property, I was able to create a script
to add the extended properties I wanted.

Thx

Mark Jackson

Home | Search | Terms | Imprint | Contact
Newsgroups Reader - provided by WiredBox.Net