|
|
You're in the
sql server (alternate)
group:Problem with HOST_NAME Function with Linked View
sql server (alternate):
First, you shouldn't crosspost to newsgroups not relevant to your problem.
Second, create a view that will simply select and display the value of HOST_NAME() and you will you see if there is a problem with it and SQL-Server 7 and a MDB file. -- Sylvain Lafontaine, ing. MVP - Technologies Virtual-PC E-mail: http://cerbermail.com/?QugbLEWINF [quoted text, click to view] "Neil" <nospam@nospam.net> wrote in message news:lra9f.1731$8c5.1137@newsread3.news.pas.earthlink.net... >I have an Access 2000 MDB file with a SQL 7 back end. I have a main table >with 50,000 records; and I have a selections table with 50,000 records for >each machine that uses the database (about 25-50). This allows each user to >have their own set of selections. > > The selections table has three fields: ID (int), Sel (bit), MachName > (varchar). ID and MachName comprise the primary key. > > I have a view that combines the main table and the entries for the > selections table for the current machine (SQL below). The view works fine > when opened in EM and QA. And if I create a pass-through query from my > Access MDB file, the results are displayed fine. > > However, if I link the view to the Access MDB file, I get "#Deleted" in > every field of every record (which seems to indicate that the records were > there and then they were gone). However, if I hard-code the machine name > into the same view instead of using HOST_NAME and then relink the view to > the MDB file, the linked view opens fine. Only when I use HOST_NAME as a > parameter in the view is there a problem with it. > > Anyone have any idea what's going on here, or have heard of any issues > with HOST_NAME and ODBC linked objects? SQL for the view is below. > > Thanks! > > Neil > > SELECT INVTRY.*, InvtrySelections.Sel, InvtrySelections.MachName > FROM dbo.INVTRY INNER JOIN > dbo.InvtrySelections ON > dbo.INVTRY.ID = dbo.InvtrySelections.ID > WHERE (dbo.InvtrySelections.MachName = HOST_NAME()) >
I have an Access 2000 MDB file with a SQL 7 back end. I have a main table
with 50,000 records; and I have a selections table with 50,000 records for each machine that uses the database (about 25-50). This allows each user to have their own set of selections. The selections table has three fields: ID (int), Sel (bit), MachName (varchar). ID and MachName comprise the primary key. I have a view that combines the main table and the entries for the selections table for the current machine (SQL below). The view works fine when opened in EM and QA. And if I create a pass-through query from my Access MDB file, the results are displayed fine. However, if I link the view to the Access MDB file, I get "#Deleted" in every field of every record (which seems to indicate that the records were there and then they were gone). However, if I hard-code the machine name into the same view instead of using HOST_NAME and then relink the view to the MDB file, the linked view opens fine. Only when I use HOST_NAME as a parameter in the view is there a problem with it. Anyone have any idea what's going on here, or have heard of any issues with HOST_NAME and ODBC linked objects? SQL for the view is below. Thanks! Neil SELECT INVTRY.*, InvtrySelections.Sel, InvtrySelections.MachName FROM dbo.INVTRY INNER JOIN dbo.InvtrySelections ON dbo.INVTRY.ID = dbo.InvtrySelections.ID WHERE (dbo.InvtrySelections.MachName = HOST_NAME())
One possible cause for seeing things like #deleted is a missing primary key
or Access is not able to determine which field is the primary key. You have said in your first post that you have defined a composite primary key on two field. This is quite possibly the source of your problem: you should try replacing it with a single field primary key. From past experience, Access seems to have a lot of trouble with linked tables or views having composite primary keys. Also, take a look at the following article; in case it might help you: http://support.microsoft.com/kb/q209123/ -- Sylvain Lafontaine, ing. MVP - Technologies Virtual-PC E-mail: http://cerbermail.com/?QugbLEWINF [quoted text, click to view] "Neil" <nospam@nospam.net> wrote in message news:hFf9f.3901$yX2.1657@newsread2.news.pas.earthlink.net... > > "Sylvain Lafontaine" <sylvain aei ca (fill the blanks, no spam please)> > wrote in message news:uQV0$Ra3FHA.2432@TK2MSFTNGP10.phx.gbl... >> First, you shouldn't crosspost to newsgroups not relevant to your >> problem. > > I wasn't aware that I had done that. > >> >> Second, create a view that will simply select and display the value of >> HOST_NAME() and you will you see if there is a problem with it and >> SQL-Server 7 and a MDB file. > > Good point. I created a view that returned the value of HOST_NAME(), and > it linked fine into the MDB. I also created a new table, gave it a > two-field PK, and used HOST_NAME() as a parameter for one of the fields in > a view. That view also linked and displayed records fine. (Didn't do a > two-table test, which would be similar to what I'm working with. But it > shows that HOST_NAME() works fine with MDB linked views.) > > Neil > > >> >> -- >> Sylvain Lafontaine, ing. >> MVP - Technologies Virtual-PC >> E-mail: http://cerbermail.com/?QugbLEWINF >> >> >> "Neil" <nospam@nospam.net> wrote in message >> news:lra9f.1731$8c5.1137@newsread3.news.pas.earthlink.net... >>>I have an Access 2000 MDB file with a SQL 7 back end. I have a main table >>>with 50,000 records; and I have a selections table with 50,000 records >>>for each machine that uses the database (about 25-50). This allows each >>>user to have their own set of selections. >>> >>> The selections table has three fields: ID (int), Sel (bit), MachName >>> (varchar). ID and MachName comprise the primary key. >>> >>> I have a view that combines the main table and the entries for the >>> selections table for the current machine (SQL below). The view works >>> fine when opened in EM and QA. And if I create a pass-through query from >>> my Access MDB file, the results are displayed fine. >>> >>> However, if I link the view to the Access MDB file, I get "#Deleted" in >>> every field of every record (which seems to indicate that the records >>> were there and then they were gone). However, if I hard-code the machine >>> name into the same view instead of using HOST_NAME and then relink the >>> view to the MDB file, the linked view opens fine. Only when I use >>> HOST_NAME as a parameter in the view is there a problem with it. >>> >>> Anyone have any idea what's going on here, or have heard of any issues >>> with HOST_NAME and ODBC linked objects? SQL for the view is below. >>> >>> Thanks! >>> >>> Neil >>> >>> SELECT INVTRY.*, InvtrySelections.Sel, InvtrySelections.MachName >>> FROM dbo.INVTRY INNER JOIN >>> dbo.InvtrySelections ON >>> dbo.INVTRY.ID = dbo.InvtrySelections.ID >>> WHERE (dbo.InvtrySelections.MachName = HOST_NAME()) >>> >> >> > >
Also, if possible, that a look on the SQL-Server with the Profiler or
activate the ODBC tracing option. This will give you the possibility of seeing what Access is trying to do. -- Sylvain Lafontaine, ing. MVP - Technologies Virtual-PC E-mail: http://cerbermail.com/?QugbLEWINF "Sylvain Lafontaine" <sylvain aei ca (fill the blanks, no spam please)> [quoted text, click to view] wrote in message news:uTA0rGd3FHA.2640@TK2MSFTNGP09.phx.gbl... > One possible cause for seeing things like #deleted is a missing primary > key or Access is not able to determine which field is the primary key. > > You have said in your first post that you have defined a composite primary > key on two field. This is quite possibly the source of your problem: you > should try replacing it with a single field primary key. From past > experience, Access seems to have a lot of trouble with linked tables or > views having composite primary keys. > > Also, take a look at the following article; in case it might help you: > http://support.microsoft.com/kb/q209123/ > > -- > Sylvain Lafontaine, ing. > MVP - Technologies Virtual-PC > E-mail: http://cerbermail.com/?QugbLEWINF > > > "Neil" <nospam@nospam.net> wrote in message > news:hFf9f.3901$yX2.1657@newsread2.news.pas.earthlink.net... >> >> "Sylvain Lafontaine" <sylvain aei ca (fill the blanks, no spam please)> >> wrote in message news:uQV0$Ra3FHA.2432@TK2MSFTNGP10.phx.gbl... >>> First, you shouldn't crosspost to newsgroups not relevant to your >>> problem. >> >> I wasn't aware that I had done that. >> >>> >>> Second, create a view that will simply select and display the value of >>> HOST_NAME() and you will you see if there is a problem with it and >>> SQL-Server 7 and a MDB file. >> >> Good point. I created a view that returned the value of HOST_NAME(), and >> it linked fine into the MDB. I also created a new table, gave it a >> two-field PK, and used HOST_NAME() as a parameter for one of the fields >> in a view. That view also linked and displayed records fine. (Didn't do a >> two-table test, which would be similar to what I'm working with. But it >> shows that HOST_NAME() works fine with MDB linked views.) >> >> Neil >> >> >>> >>> -- >>> Sylvain Lafontaine, ing. >>> MVP - Technologies Virtual-PC >>> E-mail: http://cerbermail.com/?QugbLEWINF >>> >>> >>> "Neil" <nospam@nospam.net> wrote in message >>> news:lra9f.1731$8c5.1137@newsread3.news.pas.earthlink.net... >>>>I have an Access 2000 MDB file with a SQL 7 back end. I have a main >>>>table with 50,000 records; and I have a selections table with 50,000 >>>>records for each machine that uses the database (about 25-50). This >>>>allows each user to have their own set of selections. >>>> >>>> The selections table has three fields: ID (int), Sel (bit), MachName >>>> (varchar). ID and MachName comprise the primary key. >>>> >>>> I have a view that combines the main table and the entries for the >>>> selections table for the current machine (SQL below). The view works >>>> fine when opened in EM and QA. And if I create a pass-through query >>>> from my Access MDB file, the results are displayed fine. >>>> >>>> However, if I link the view to the Access MDB file, I get "#Deleted" in >>>> every field of every record (which seems to indicate that the records >>>> were there and then they were gone). However, if I hard-code the >>>> machine name into the same view instead of using HOST_NAME and then >>>> relink the view to the MDB file, the linked view opens fine. Only when >>>> I use HOST_NAME as a parameter in the view is there a problem with it. >>>> >>>> Anyone have any idea what's going on here, or have heard of any issues >>>> with HOST_NAME and ODBC linked objects? SQL for the view is below. >>>> >>>> Thanks! >>>> >>>> Neil >>>> >>>> SELECT INVTRY.*, InvtrySelections.Sel, InvtrySelections.MachName >>>> FROM dbo.INVTRY INNER JOIN >>>> dbo.InvtrySelections ON >>>> dbo.INVTRY.ID = dbo.InvtrySelections.ID >>>> WHERE (dbo.InvtrySelections.MachName = HOST_NAME()) >>>> >>> >>> >> >> > >
Neil (nospam@nospam.net) writes:
[quoted text, click to view] > SELECT INVTRY.*, InvtrySelections.Sel, InvtrySelections.MachName > FROM dbo.INVTRY INNER JOIN > dbo.InvtrySelections ON > dbo.INVTRY.ID = dbo.InvtrySelections.ID > WHERE (dbo.InvtrySelections.MachName = HOST_NAME()) Now that I see the entire view, I repeat what I said before: make MachName nvarchar, and put the clustered index on this column. -- Erland Sommarskog, SQL Server MVP, esquel@sommarskog.se Books Online for SQL Server SP3 at http://www.microsoft.com/sql/techinfo/productdoc/2000/books.asp
Obscure footnote:
[quoted text, click to view] > any floating point columns in your data (including > datetime as these are stored as floating point numbers) SQL Server doesn't store datetime as double. Access does, and the problem arises because of the rounding error in the conversion between the Access version and the SQL Server version, even when values are not 'stored' in Access at all. (david) [quoted text, click to view] "Trevor Best" <nospam@localhost.invalid> wrote in message news:43656dd0$0$345$da0feed9@news.zen.co.uk... > Neil wrote: ..> > I've not had any problems with Host_name() as a parameter, as the only > records I retrieve are for my particular machine there is very little > point in returning that column so I never ask the server for it as I > know the value already. > > A couple of things you need to know about Access and SQL Server, firstly > bit fields should be made NOT NULL and default to 0 as Access interprets > these as Jet Yes/No columns and treats them accordingly so it expects a > value to be there (In Access/Jet, a Yes/No column cannot be null and > defaults to 0). The results otherwise can be unpredictable. > > Secondly, if you have any floating point columns in your data (including > datetime as these are stored as floating point numbers) then you most > probably need a timestamp column as floating point errors can cause the > #Deleted condition you describe.
"Sylvain Lafontaine" <sylvain aei ca (fill the blanks, no spam please)> [quoted text, click to view] wrote in message news:uQV0$Ra3FHA.2432@TK2MSFTNGP10.phx.gbl... > First, you shouldn't crosspost to newsgroups not relevant to your problem. I wasn't aware that I had done that. [quoted text, click to view] > > Second, create a view that will simply select and display the value of > HOST_NAME() and you will you see if there is a problem with it and > SQL-Server 7 and a MDB file. Good point. I created a view that returned the value of HOST_NAME(), and it linked fine into the MDB. I also created a new table, gave it a two-field PK, and used HOST_NAME() as a parameter for one of the fields in a view. That view also linked and displayed records fine. (Didn't do a two-table test, which would be similar to what I'm working with. But it shows that HOST_NAME() works fine with MDB linked views.) Neil [quoted text, click to view] > > -- > Sylvain Lafontaine, ing. > MVP - Technologies Virtual-PC > E-mail: http://cerbermail.com/?QugbLEWINF > > > "Neil" <nospam@nospam.net> wrote in message > news:lra9f.1731$8c5.1137@newsread3.news.pas.earthlink.net... >>I have an Access 2000 MDB file with a SQL 7 back end. I have a main table >>with 50,000 records; and I have a selections table with 50,000 records for >>each machine that uses the database (about 25-50). This allows each user >>to have their own set of selections. >> >> The selections table has three fields: ID (int), Sel (bit), MachName >> (varchar). ID and MachName comprise the primary key. >> >> I have a view that combines the main table and the entries for the >> selections table for the current machine (SQL below). The view works fine >> when opened in EM and QA. And if I create a pass-through query from my >> Access MDB file, the results are displayed fine. >> >> However, if I link the view to the Access MDB file, I get "#Deleted" in >> every field of every record (which seems to indicate that the records >> were there and then they were gone). However, if I hard-code the machine >> name into the same view instead of using HOST_NAME and then relink the >> view to the MDB file, the linked view opens fine. Only when I use >> HOST_NAME as a parameter in the view is there a problem with it. >> >> Anyone have any idea what's going on here, or have heard of any issues >> with HOST_NAME and ODBC linked objects? SQL for the view is below. >> >> Thanks! >> >> Neil >> >> SELECT INVTRY.*, InvtrySelections.Sel, InvtrySelections.MachName >> FROM dbo.INVTRY INNER JOIN >> dbo.InvtrySelections ON >> dbo.INVTRY.ID = dbo.InvtrySelections.ID >> WHERE (dbo.InvtrySelections.MachName = HOST_NAME()) >> > >
After I got your note I did go ahead and make MachName nchar, as BOL says
that HOST_NAME() returns that type, and the sample it showed of storing its return value in a table used an nchar(30) field. The InvtrySelections table had the PK (ID/MachName) as the clustered index. I created a second index on MachName alone, and it made it the clustered index. With the above two changes, the results were the same. Still getting "#Deleted". Neil [quoted text, click to view] "Erland Sommarskog" <esquel@sommarskog.se> wrote in message news:Xns970061F02065Yazorman@127.0.0.1... > Neil (nospam@nospam.net) writes: >> SELECT INVTRY.*, InvtrySelections.Sel, InvtrySelections.MachName >> FROM dbo.INVTRY INNER JOIN >> dbo.InvtrySelections ON >> dbo.INVTRY.ID = dbo.InvtrySelections.ID >> WHERE (dbo.InvtrySelections.MachName = HOST_NAME()) > > Now that I see the entire view, I repeat what I said before: make > MachName nvarchar, and put the clustered index on this column. > > > -- > Erland Sommarskog, SQL Server MVP, esquel@sommarskog.se > > Books Online for SQL Server SP3 at > http://www.microsoft.com/sql/techinfo/productdoc/2000/books.asp >
[quoted text, click to view] > I've not had any problems with Host_name() as a parameter, as the only > records I retrieve are for my particular machine there is very little > point in returning that column so I never ask the server for it as I know > the value already. > > A couple of things you need to know about Access and SQL Server, firstly > bit fields should be made NOT NULL and default to 0 as Access interprets > these as Jet Yes/No columns and treats them accordingly so it expects a > value to be there (In Access/Jet, a Yes/No column cannot be null and > defaults to 0). The results otherwise can be unpredictable. Yes, the bit field is Not Null and defaults to zero. [quoted text, click to view] > > Secondly, if you have any floating point columns in your data (including > datetime as these are stored as floating point numbers) then you most > probably need a timestamp column as floating point errors can cause the > #Deleted condition you describe. I don't have any floating point columns in my table. However, I went ahead and added a timestamp field anyway. Same results. Neil
Hello, everyone.
I've made some progress with this strange situation. I played around with different scenarios of the view with HOST_NAME that won't work when linked to the MDB file, removing most fields, trying just one table, then the other, and kept getting the "#Deleted" results. However, I found then when I didn't assign a logical primary key when I linked the view, the results displayed fine! That only makes the situation stranger. But there it is. In another post here I noted that I had created a test table with a two-field PK, one of which contained the HOST_NAME value, and created a view which returned records from this test table, with HOST_NAME() as a parameter for that field. When I linked that view to the MDB file, selecting the two PK fields as the logical primary key, it worked fine. So it's not all logical primary keys that it has problems with. Neil [quoted text, click to view] "Neil" <nospam@nospam.net> wrote in message news:lra9f.1731$8c5.1137@newsread3.news.pas.earthlink.net... >I have an Access 2000 MDB file with a SQL 7 back end. I have a main table >with 50,000 records; and I have a selections table with 50,000 records for >each machine that uses the database (about 25-50). This allows each user to >have their own set of selections. > > The selections table has three fields: ID (int), Sel (bit), MachName > (varchar). ID and MachName comprise the primary key. > > I have a view that combines the main table and the entries for the > selections table for the current machine (SQL below). The view works fine > when opened in EM and QA. And if I create a pass-through query from my > Access MDB file, the results are displayed fine. > > However, if I link the view to the Access MDB file, I get "#Deleted" in > every field of every record (which seems to indicate that the records were > there and then they were gone). However, if I hard-code the machine name > into the same view instead of using HOST_NAME and then relink the view to > the MDB file, the linked view opens fine. Only when I use HOST_NAME as a > parameter in the view is there a problem with it. > > Anyone have any idea what's going on here, or have heard of any issues > with HOST_NAME and ODBC linked objects? SQL for the view is below. > > Thanks! > > Neil > > SELECT INVTRY.*, InvtrySelections.Sel, InvtrySelections.MachName > FROM dbo.INVTRY INNER JOIN > dbo.InvtrySelections ON > dbo.INVTRY.ID = dbo.InvtrySelections.ID > WHERE (dbo.InvtrySelections.MachName = HOST_NAME()) >
Re. the composite primary key, note that in my test I did create a table
with a composite primary key, to simulate the situation, and it worked fine. I followed up on that in my more recent post in this thread, which shows that the situation is now even more bizarre. Regarding changing to a single field primary key, I do not believe that is possible. The main table has a single-field primary key (int, identity), and the other table (which has a one-to-one relationship with the main table) has a dual primary key -- one field corresponding to the main table's primary key, and the other containing the machine name. That table has to have both fields in the primary key. The resulting view can have a one-field or two-field virtual primary key when linked in access, depending on whether or not I include the machine name field in the resultset. Seems to me that it's better to include it and have a two-field primary key, so that Access can determine the record. Neil "Sylvain Lafontaine" <sylvain aei ca (fill the blanks, no spam please)> [quoted text, click to view] wrote in message news:uTA0rGd3FHA.2640@TK2MSFTNGP09.phx.gbl... > One possible cause for seeing things like #deleted is a missing primary > key or Access is not able to determine which field is the primary key. > > You have said in your first post that you have defined a composite primary > key on two field. This is quite possibly the source of your problem: you > should try replacing it with a single field primary key. From past > experience, Access seems to have a lot of trouble with linked tables or > views having composite primary keys. > > Also, take a look at the following article; in case it might help you: > http://support.microsoft.com/kb/q209123/ > > -- > Sylvain Lafontaine, ing. > MVP - Technologies Virtual-PC > E-mail: http://cerbermail.com/?QugbLEWINF > > > "Neil" <nospam@nospam.net> wrote in message > news:hFf9f.3901$yX2.1657@newsread2.news.pas.earthlink.net... >> >> "Sylvain Lafontaine" <sylvain aei ca (fill the blanks, no spam please)> >> wrote in message news:uQV0$Ra3FHA.2432@TK2MSFTNGP10.phx.gbl... >>> First, you shouldn't crosspost to newsgroups not relevant to your >>> problem. >> >> I wasn't aware that I had done that. >> >>> >>> Second, create a view that will simply select and display the value of >>> HOST_NAME() and you will you see if there is a problem with it and >>> SQL-Server 7 and a MDB file. >> >> Good point. I created a view that returned the value of HOST_NAME(), and >> it linked fine into the MDB. I also created a new table, gave it a >> two-field PK, and used HOST_NAME() as a parameter for one of the fields >> in a view. That view also linked and displayed records fine. (Didn't do a >> two-table test, which would be similar to what I'm working with. But it >> shows that HOST_NAME() works fine with MDB linked views.) >> >> Neil >> >> >>> >>> -- >>> Sylvain Lafontaine, ing. >>> MVP - Technologies Virtual-PC >>> E-mail: http://cerbermail.com/?QugbLEWINF >>> >>> >>> "Neil" <nospam@nospam.net> wrote in message >>> news:lra9f.1731$8c5.1137@newsread3.news.pas.earthlink.net... >>>>I have an Access 2000 MDB file with a SQL 7 back end. I have a main >>>>table with 50,000 records; and I have a selections table with 50,000 >>>>records for each machine that uses the database (about 25-50). This >>>>allows each user to have their own set of selections. >>>> >>>> The selections table has three fields: ID (int), Sel (bit), MachName >>>> (varchar). ID and MachName comprise the primary key. >>>> >>>> I have a view that combines the main table and the entries for the >>>> selections table for the current machine (SQL below). The view works >>>> fine when opened in EM and QA. And if I create a pass-through query >>>> from my Access MDB file, the results are displayed fine. >>>> >>>> However, if I link the view to the Access MDB file, I get "#Deleted" in >>>> every field of every record (which seems to indicate that the records >>>> were there and then they were gone). However, if I hard-code the >>>> machine name into the same view instead of using HOST_NAME and then >>>> relink the view to the MDB file, the linked view opens fine. Only when >>>> I use HOST_NAME as a parameter in the view is there a problem with it. >>>> >>>> Anyone have any idea what's going on here, or have heard of any issues >>>> with HOST_NAME and ODBC linked objects? SQL for the view is below. >>>> >>>> Thanks! >>>> >>>> Neil >>>> >>>> SELECT INVTRY.*, InvtrySelections.Sel, InvtrySelections.MachName >>>> FROM dbo.INVTRY INNER JOIN >>>> dbo.InvtrySelections ON >>>> dbo.INVTRY.ID = dbo.InvtrySelections.ID >>>> WHERE (dbo.InvtrySelections.MachName = HOST_NAME()) >>>> >>> >>> >> >> > >
ODBC tracing might show something. Now sure what Profiler would yield, since
SQL Server seems to be returning the records without any problem. Neil "Sylvain Lafontaine" <sylvain aei ca (fill the blanks, no spam please)> [quoted text, click to view] wrote in message news:%23sye%23Id3FHA.4076@TK2MSFTNGP15.phx.gbl... > Also, if possible, that a look on the SQL-Server with the Profiler or > activate the ODBC tracing option. This will give you the possibility of > seeing what Access is trying to do. > > -- > Sylvain Lafontaine, ing. > MVP - Technologies Virtual-PC > E-mail: http://cerbermail.com/?QugbLEWINF > > > "Sylvain Lafontaine" <sylvain aei ca (fill the blanks, no spam please)> > wrote in message news:uTA0rGd3FHA.2640@TK2MSFTNGP09.phx.gbl... >> One possible cause for seeing things like #deleted is a missing primary >> key or Access is not able to determine which field is the primary key. >> >> You have said in your first post that you have defined a composite >> primary key on two field. This is quite possibly the source of your >> problem: you should try replacing it with a single field primary key. >> From past experience, Access seems to have a lot of trouble with linked >> tables or views having composite primary keys. >> >> Also, take a look at the following article; in case it might help you: >> http://support.microsoft.com/kb/q209123/ >> >> -- >> Sylvain Lafontaine, ing. >> MVP - Technologies Virtual-PC >> E-mail: http://cerbermail.com/?QugbLEWINF >> >> >> "Neil" <nospam@nospam.net> wrote in message >> news:hFf9f.3901$yX2.1657@newsread2.news.pas.earthlink.net... >>> >>> "Sylvain Lafontaine" <sylvain aei ca (fill the blanks, no spam please)> >>> wrote in message news:uQV0$Ra3FHA.2432@TK2MSFTNGP10.phx.gbl... >>>> First, you shouldn't crosspost to newsgroups not relevant to your >>>> problem. >>> >>> I wasn't aware that I had done that. >>> >>>> >>>> Second, create a view that will simply select and display the value of >>>> HOST_NAME() and you will you see if there is a problem with it and >>>> SQL-Server 7 and a MDB file. >>> >>> Good point. I created a view that returned the value of HOST_NAME(), and >>> it linked fine into the MDB. I also created a new table, gave it a >>> two-field PK, and used HOST_NAME() as a parameter for one of the fields >>> in a view. That view also linked and displayed records fine. (Didn't do >>> a two-table test, which would be similar to what I'm working with. But >>> it shows that HOST_NAME() works fine with MDB linked views.) >>> >>> Neil >>> >>> >>>> >>>> -- >>>> Sylvain Lafontaine, ing. >>>> MVP - Technologies Virtual-PC >>>> E-mail: http://cerbermail.com/?QugbLEWINF >>>> >>>> >>>> "Neil" <nospam@nospam.net> wrote in message >>>> news:lra9f.1731$8c5.1137@newsread3.news.pas.earthlink.net... >>>>>I have an Access 2000 MDB file with a SQL 7 back end. I have a main >>>>>table with 50,000 records; and I have a selections table with 50,000 >>>>>records for each machine that uses the database (about 25-50). This >>>>>allows each user to have their own set of selections. >>>>> >>>>> The selections table has three fields: ID (int), Sel (bit), MachName >>>>> (varchar). ID and MachName comprise the primary key. >>>>> >>>>> I have a view that combines the main table and the entries for the >>>>> selections table for the current machine (SQL below). The view works >>>>> fine when opened in EM and QA. And if I create a pass-through query >>>>> from my Access MDB file, the results are displayed fine. >>>>> >>>>> However, if I link the view to the Access MDB file, I get "#Deleted" >>>>> in every field of every record (which seems to indicate that the >>>>> records were there and then they were gone). However, if I hard-code >>>>> the machine name into the same view instead of using HOST_NAME and >>>>> then relink the view to the MDB file, the linked view opens fine. Only >>>>> when I use HOST_NAME as a parameter in the view is there a problem >>>>> with it. >>>>> >>>>> Anyone have any idea what's going on here, or have heard of any issues >>>>> with HOST_NAME and ODBC linked objects? SQL for the view is below. >>>>> >>>>> Thanks! >>>>> >>>>> Neil >>>>> >>>>> SELECT INVTRY.*, InvtrySelections.Sel, InvtrySelections.MachName >>>>> FROM dbo.INVTRY INNER JOIN >>>>> dbo.InvtrySelections ON >>>>> dbo.INVTRY.ID = dbo.InvtrySelections.ID >>>>> WHERE (dbo.InvtrySelections.MachName = HOST_NAME()) >>>>> >>>> >>>> >>> >>> >> >> > >
It is not a requirement for relationships to be based on primary keys; so
nothing forbid you to a add a new field as the primary key for the other table and keep the two other fields for your relationship. Using a machine name as part of an index is also a bad idea: you should create another table, put these machine names there and use their identity values for the second table. -- Sylvain Lafontaine, ing. MVP - Technologies Virtual-PC E-mail: http://cerbermail.com/?QugbLEWINF [quoted text, click to view] "Neil" <nospam@nospam.net> wrote in message news:U7h9f.1895$8c5.1662@newsread3.news.pas.earthlink.net... > Re. the composite primary key, note that in my test I did create a table > with a composite primary key, to simulate the situation, and it worked > fine. I followed up on that in my more recent post in this thread, which > shows that the situation is now even more bizarre. > > Regarding changing to a single field primary key, I do not believe that is > possible. The main table has a single-field primary key (int, identity), > and the other table (which has a one-to-one relationship with the main > table) has a dual primary key -- one field corresponding to the main > table's primary key, and the other containing the machine name. That table > has to have both fields in the primary key. > > The resulting view can have a one-field or two-field virtual primary key > when linked in access, depending on whether or not I include the machine > name field in the resultset. Seems to me that it's better to include it > and have a two-field primary key, so that Access can determine the record. > > Neil > > > "Sylvain Lafontaine" <sylvain aei ca (fill the blanks, no spam please)> > wrote in message news:uTA0rGd3FHA.2640@TK2MSFTNGP09.phx.gbl... >> One possible cause for seeing things like #deleted is a missing primary >> key or Access is not able to determine which field is the primary key. >> >> You have said in your first post that you have defined a composite >> primary key on two field. This is quite possibly the source of your >> problem: you should try replacing it with a single field primary key. >> From past experience, Access seems to have a lot of trouble with linked >> tables or views having composite primary keys. >> >> Also, take a look at the following article; in case it might help you: >> http://support.microsoft.com/kb/q209123/ >> >> -- >> Sylvain Lafontaine, ing. >> MVP - Technologies Virtual-PC >> E-mail: http://cerbermail.com/?QugbLEWINF >> >> >> "Neil" <nospam@nospam.net> wrote in message >> news:hFf9f.3901$yX2.1657@newsread2.news.pas.earthlink.net... >>> >>> "Sylvain Lafontaine" <sylvain aei ca (fill the blanks, no spam please)> >>> wrote in message news:uQV0$Ra3FHA.2432@TK2MSFTNGP10.phx.gbl... >>>> First, you shouldn't crosspost to newsgroups not relevant to your >>>> problem. >>> >>> I wasn't aware that I had done that. >>> >>>> >>>> Second, create a view that will simply select and display the value of >>>> HOST_NAME() and you will you see if there is a problem with it and >>>> SQL-Server 7 and a MDB file. >>> >>> Good point. I created a view that returned the value of HOST_NAME(), and >>> it linked fine into the MDB. I also created a new table, gave it a >>> two-field PK, and used HOST_NAME() as a parameter for one of the fields >>> in a view. That view also linked and displayed records fine. (Didn't do >>> a two-table test, which would be similar to what I'm working with. But >>> it shows that HOST_NAME() works fine with MDB linked views.) >>> >>> Neil >>> >>> >>>> >>>> -- >>>> Sylvain Lafontaine, ing. >>>> MVP - Technologies Virtual-PC >>>> E-mail: http://cerbermail.com/?QugbLEWINF >>>> >>>> >>>> "Neil" <nospam@nospam.net> wrote in message >>>> news:lra9f.1731$8c5.1137@newsread3.news.pas.earthlink.net... >>>>>I have an Access 2000 MDB file with a SQL 7 back end. I have a main >>>>>table with 50,000 records; and I have a selections table with 50,000 >>>>>records for each machine that uses the database (about 25-50). This >>>>>allows each user to have their own set of selections. >>>>> >>>>> The selections table has three fields: ID (int), Sel (bit), MachName >>>>> (varchar). ID and MachName comprise the primary key. >>>>> >>>>> I have a view that combines the main table and the entries for the >>>>> selections table for the current machine (SQL below). The view works >>>>> fine when opened in EM and QA. And if I create a pass-through query >>>>> from my Access MDB file, the results are displayed fine. >>>>> >>>>> However, if I link the view to the Access MDB file, I get "#Deleted" >>>>> in every field of every record (which seems to indicate that the >>>>> records were there and then they were gone). However, if I hard-code >>>>> the machine name into the same view instead of using HOST_NAME and >>>>> then relink the view to the MDB file, the linked view opens fine. Only >>>>> when I use HOST_NAME as a parameter in the view is there a problem >>>>> with it. >>>>> >>>>> Anyone have any idea what's going on here, or have heard of any issues >>>>> with HOST_NAME and ODBC linked objects? SQL for the view is below. >>>>> >>>>> Thanks! >>>>> >>>>> Neil >>>>> >>>>> SELECT INVTRY.*, InvtrySelections.Sel, InvtrySelections.MachName >>>>> FROM dbo.INVTRY INNER JOIN >>>>> dbo.InvtrySelections ON >>>>> dbo.INVTRY.ID = dbo.InvtrySelections.ID >>>>> WHERE (dbo.InvtrySelections.MachName = HOST_NAME()) >>>>> >>>> >>>> >>> >>> >> >> > >
[quoted text, click to view]
Neil wrote: > I have an Access 2000 MDB file with a SQL 7 back end. I have a main table > with 50,000 records; and I have a selections table with 50,000 records for > each machine that uses the database (about 25-50). This allows each user to > have their own set of selections. > > The selections table has three fields: ID (int), Sel (bit), MachName > (varchar). ID and MachName comprise the primary key. > > I have a view that combines the main table and the entries for the > selections table for the current machine (SQL below). The view works fine > when opened in EM and QA. And if I create a pass-through query from my > Access MDB file, the results are displayed fine. > > However, if I link the view to the Access MDB file, I get "#Deleted" in > every field of every record (which seems to indicate that the records were > there and then they were gone). However, if I hard-code the machine name > into the same view instead of using HOST_NAME and then relink the view to > the MDB file, the linked view opens fine. Only when I use HOST_NAME as a > parameter in the view is there a problem with it. > > Anyone have any idea what's going on here, or have heard of any issues with > HOST_NAME and ODBC linked objects? SQL for the view is below. I've not had any problems with Host_name() as a parameter, as the only records I retrieve are for my particular machine there is very little point in returning that column so I never ask the server for it as I know the value already. A couple of things you need to know about Access and SQL Server, firstly bit fields should be made NOT NULL and default to 0 as Access interprets these as Jet Yes/No columns and treats them accordingly so it expects a value to be there (In Access/Jet, a Yes/No column cannot be null and defaults to 0). The results otherwise can be unpredictable. Secondly, if you have any floating point columns in your data (including datetime as these are stored as floating point numbers) then you most probably need a timestamp column as floating point errors can cause the
Don't see what you're looking for? Try a search.
|
January 2003
June 2003
July 2003
August 2003
September 2003
October 2003
November 2003
December 2003
January 2004
February 2004
March 2004
April 2004
May 2004
June 2004
July 2004
August 2004
September 2004
October 2004
November 2004
December 2004
January 2005
February 2005
March 2005
April 2005
May 2005
June 2005
July 2005
August 2005
September 2005
October 2005
November 2005
December 2005
January 2006
February 2006
March 2006
April 2006
May 2006
June 2006
July 2006
August 2006
September 2006
October 2006
November 2006
December 2006
January 2007
February 2007
March 2007
April 2007
May 2007
June 2007
July 2007
August 2007
September 2007
October 2007
| home · blog · groups | Questions? Comments? Contact the dn |