Accessing Data directly from a SqlDataSource?

First let me give you a little back ground on me. I'm very new to the ASP, ASP.NET, Visual Studio, Sql Server, Frameworks...thing. I am coming over from a PHP/MySql background of over 5 years. The change over to VBScript and VB has been to tough and I have a basic liking for the Visual Studio 2005 and the ease of putting things together. However, I have come across something that to me seems like it should be relatively simple, but haven't been able to find the documentation or samples to describe what I'm looking to do.

Rough Need:

1. Start with a form will a couple labels and a singe textbox to get the lookup date from an user.

2. Query one table/view based on the users choice of date and select only one field of returned data.(Doing this by itself is not a problem and I can display my results in a Gridview, but this is where it starts getting tricky and the gridviews won't work for me.)

3. If there is something returned, I need to start a HTML table layout or possibly some form of a Gridview(I don't see how I would use the Gridview) and start a loop, adding the first returned row from this query into the first cell.

4. Now, based on that same User Date and the returned row value from the previous query, I need to query another Table/view and return another single field, which might return 1 or multiple rows, which I need to start a loop to display unique items in cells under the first on above.

5. Based on the original User Date and each returned row from the first query, I need to query two other Table/views and get some additional information. 4-5 fields will be returned and be displayed on one row in the number of necessary columns.

6. This would finish the first row from the first query, so I would need to loop back up to see if there were any further results and continue looping until the get to the last of the results from the first query.

7. Finally, I would just need to close up the Table/gridview.

The basic results I'm looking for would be similar to the following:

Results for 10/11/2005

Field name 1Field name 2Field name 3Field name 4Field name 5

First Result from query 1
1 of 4 results from Query 2, but only 1 unique result

Info from Query 3

Info from Query 3

Info from Query 3

Info from Query 4Info from Query 4Info from Query 3Info from Query 3.

Info from Query 3

Info from Query 4
Info from Query 4Info from Query 3

Info from Query 3

Info from Query 3

Info from Query 4
Info from Query 4Info from Query 3Info from Query 3

Info from Query 3

Info from Query 4Info from Query 4

Second Result from query 1
First result from Query 2 after looping though the first query
Second result from Query 2 after looping though the first query
Info from Query 3

Info from Query 3

Info from Query 3

Info from Query 4Info from Query 4Info from Query 3Info from Query 3.

Info from Query 3

Info from Query 4
Info from Query 4Info from Query 3

Info from Query 3

Info from Query 3

Info from Query 4
Info from Query 4Info from Query 3Info from Query 3

Info from Query 3

Info from Query 4Info from Query 4

It seems me from what I have read and slowly figuring out, is that I should be able to directly access the DataSet returned by four SqlDataSources, one for each of the above querys and then just write my own VB to handle the necessary looping, table format and such. I can easily add the for SqlDataSources to the page and add a Gridview for each one and get 4 separate chunks of info, but can't see a way with GridViews to intermingle the info like displayed above.

So, if it can be done with Gridviews, then I would love to see how that is done. But, if someone could explain to me how I access the DataSets directly that I get from the 4 SqlDataSources, then that would be ok too. I have figured enough out with VB, that I can write the code to do my looping requirements, if I can just access the information I get back. Thanks for reading all the way through this long post.

Jack

First let me apologize for the mis-spellings and the two links in my sample layout. I did some copy-n-pasting, then changed the wording, but forgot to remove the link behind. I didn't see any way on this forum to be able to Edit my own post to make the necessary corrections.

Second, is this as big of a problem as it seems, since know one made any replies to it? From what little research I've done, it looks like this should be possible with nested Repeaters, but I just can't seem to figure out how to put it all together so that the second SqlDataSource can use each returned value from the results of the first SqlDataSource to get the next set of records and then again with the third and fourth SqlDataSources.

If someone could just give a very short example of a form with a single texbox and submit button, that on postback, you could manually loop through the results returned by a single field onto the page, then I think that would give me some direction here. This is one of those cases that I don't think I want to use a Control to display the returned information, I just need to know how to manually access that returned info. Thanks again.

Jack

Accessing a Report Server from within a winform

Sometime back I posted a message asking about how to access a Report Server
from within a winform. I got a message back that said the following:
"What I did is incorporate the WebBrowser ActiveX object onto a win form and
the set its URL to the URL that would be in a browser. So far this has
worked extrememely well, but I haven't deployed it yet."
My question is, how does on do this? That is, I so no WebBrowser ActiveX
object in the toolbox that can be dragged and dropped onto a winform. It
would help if from a winform I was able to access the Report Server. How
might this be done?You have a couple of options:
Using URL Access:
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/rsprog/htm/rsp_prog_intro_6f6q.asp?frame=true
Using SOAP:
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/rsprog/htm/rsp_prog_intro_7vqa.asp?frame=true
--
Ravi Mumulla (Microsoft)
SQL Server Reporting Services
This posting is provided "AS IS" with no warranties, and confers no rights.
"Woody Splawn" <nospam@.splawns.com> wrote in message
news:OMvqySZgEHA.596@.TK2MSFTNGP11.phx.gbl...
> Sometime back I posted a message asking about how to access a Report
Server
> from within a winform. I got a message back that said the following:
> "What I did is incorporate the WebBrowser ActiveX object onto a win form
and
> the set its URL to the URL that would be in a browser. So far this has
> worked extrememely well, but I haven't deployed it yet."
> My question is, how does on do this? That is, I so no WebBrowser ActiveX
> object in the toolbox that can be dragged and dropped onto a winform. It
> would help if from a winform I was able to access the Report Server. How
> might this be done?
>
>|||Woody:
In your forms application right click on the Toolbox and select
"Customize". On the COM components tab in the next dialog select
'Microsoft Web Browser' and click OK.
You should now have a web browser control in the Toolbox you can drop
on your form. It's a bit clunky since it is ActiveX based, but it does
work. VS2005 has a native component to do this, but that doesn't solve
today's problems now does it? :)
Hope this helps,
--
Scott
http://www.OdeToCode.com
On Fri, 13 Aug 2004 17:21:55 -0700, "Woody Splawn"
<nospam@.splawns.com> wrote:
>Sometime back I posted a message asking about how to access a Report Server
>from within a winform. I got a message back that said the following:
>"What I did is incorporate the WebBrowser ActiveX object onto a win form and
>the set its URL to the URL that would be in a browser. So far this has
>worked extrememely well, but I haven't deployed it yet."
>My question is, how does on do this? That is, I so no WebBrowser ActiveX
>object in the toolbox that can be dragged and dropped onto a winform. It
>would help if from a winform I was able to access the Report Server. How
>might this be done?
>

Access/Enterprise Manager Diagrams Incompatible?

I asked this one a while back but I still haven't got it figured out yet.
What my problem boils down to is that SQL server diagrams created with
Access XP (latest version with patches) created through an ADP and diagrams
created with enterprise manager (latest version + patches) seem to be
completely incompatible. Whenever I open a diagram created with one tool in
the other tool, the tool doing the opening crashes, completely crashes at
that. I'm working on a project and the DB is growing to a complexity where I
really need a reliable way to share the diagrams with my team members. I
don't want to put too much work into good diagrams with one tool if they're
going to be useless in the other. Other developers I have spoken with don't
seem to have this problem. Have I missed a patch? Is this a known
incompatibility? Is something configured wrong? I'm at wits end.
Sorry for the cross posting but this anomaly is really annoying me and we
need to use both Enterprise Manager and Access and this is holding us up
somewhat. So I'm hoping to fish for answers in the largest pool. Thanks in
advance to anyone who can give me a clue on this one!
Jon
I have used both interchangeably without a problem. It would seem a drastic
step to start uninstalling/reinstalling without knowing exactly what the
problem may be or if it will be cured. I suggest just creating and viewing
all the diagrams in Access because everyone should have that installed.
Arvin Meyer, MCP, MVP
Microsoft Access
Free Access downloads:
http://www.datastrat.com
http://www.mvps.org/access
"Jon" <jonremovemewest@.msn.com> wrote in message
news:ehiDwrHcEHA.2476@.TK2MSFTNGP09.phx.gbl...
> I asked this one a while back but I still haven't got it figured out yet.
> What my problem boils down to is that SQL server diagrams created with
> Access XP (latest version with patches) created through an ADP and
diagrams
> created with enterprise manager (latest version + patches) seem to be
> completely incompatible. Whenever I open a diagram created with one tool
in
> the other tool, the tool doing the opening crashes, completely crashes at
> that. I'm working on a project and the DB is growing to a complexity where
I
> really need a reliable way to share the diagrams with my team members. I
> don't want to put too much work into good diagrams with one tool if
they're
> going to be useless in the other. Other developers I have spoken with
don't
> seem to have this problem. Have I missed a patch? Is this a known
> incompatibility? Is something configured wrong? I'm at wits end.
> Sorry for the cross posting but this anomaly is really annoying me and we
> need to use both Enterprise Manager and Access and this is holding us up
> somewhat. So I'm hoping to fish for answers in the largest pool. Thanks in
> advance to anyone who can give me a clue on this one!
>
> Jon
>
|||Which version of Access do you use? Access2002(XP) or Access2003? Since I
have the same problem with SQL Server2000(Developer edition) and AccessXP,
i.e. Diagram created in one program crashes othe other program when opening.
I just wonder whether Access 2003 has the same problem or not. At least,
with AccessXP, it is not "Just me" thing.
"Arvin Meyer" <a@.m.com> wrote in message
news:ObcInaKcEHA.3480@.TK2MSFTNGP11.phx.gbl...
> I have used both interchangeably without a problem. It would seem a
drastic[vbcol=seagreen]
> step to start uninstalling/reinstalling without knowing exactly what the
> problem may be or if it will be cured. I suggest just creating and viewing
> all the diagrams in Access because everyone should have that installed.
> --
> Arvin Meyer, MCP, MVP
> Microsoft Access
> Free Access downloads:
> http://www.datastrat.com
> http://www.mvps.org/access
> "Jon" <jonremovemewest@.msn.com> wrote in message
> news:ehiDwrHcEHA.2476@.TK2MSFTNGP09.phx.gbl...
yet.[vbcol=seagreen]
> diagrams
> in
at[vbcol=seagreen]
where[vbcol=seagreen]
> I
> they're
> don't
we[vbcol=seagreen]
in
>
|||I forgot to mention that the diagram created in Enterprise Manager also
crashes Visual Studio2003, if I try to open it in Server Explorer. So, the
problem seems from Enterprise Manager, rather than AccessXP. As I said, I am
using SQL Server2000 developer edition with SP3.
"Norman Yuan" <nobody@.nowhere.no> wrote in message
news:OyDRGNMcEHA.3476@.tk2msftngp13.phx.gbl...
> Which version of Access do you use? Access2002(XP) or Access2003? Since I
> have the same problem with SQL Server2000(Developer edition) and AccessXP,
> i.e. Diagram created in one program crashes othe other program when
opening.[vbcol=seagreen]
> I just wonder whether Access 2003 has the same problem or not. At least,
> with AccessXP, it is not "Just me" thing.
>
> "Arvin Meyer" <a@.m.com> wrote in message
> news:ObcInaKcEHA.3480@.TK2MSFTNGP11.phx.gbl...
> drastic
viewing[vbcol=seagreen]
> yet.
tool[vbcol=seagreen]
> at
> where
I[vbcol=seagreen]
> we
up[vbcol=seagreen]
Thanks
> in
>
|||I'm on Access XP, I also have 2000 installed I bet it would be the same
there though. I'd have to check to be sure. Yeah it looks like some of us
have this problem and some aren't, I'm hoping that someone knows something
as I'm really starting to like ADPs but I need this to work correctly. I
really don't want to go through the whole reinstall rigmarole either as it's
a huge time sink and I have real work to do(plus like you all said there's
no guarantee that it will fix anything).
Jon
|||Ditto here on the SQL config...SQL 2000 developer edition with SP3 applied.
Although I tried it with enterprise edition and got the same bad results.
Jon
|||There's a thread on microsoft.public.sqlserver.server called "Diagram Editor
doesn't work in SQLServer 2000", it says something about a dll conflict
caused by installation of VB6. I do have VB 6 installed so I wonder if this
is the culprit. What do you all think? I'm not fooling with my registrations
until I know what's up with this. What do you all have installed? Any
suggestions.
Jon
|||I don't think there's any question but that it is a DLL conflict, Jon. The
issue is, of course, which DLL, and what to do about it.
I had problems with the diagram editor on my old PC, which had Visual Studio
6 (including VB6) installed. I do not have problems on my new PC, which has
never had Visual Studio 6 installed. So yes, it would seem likely that the
problem DLL is installed by Visual Studio 6. But that doesn't rule out the
possibility that it may also be installed by other applications.
Brendan Reynolds (MVP)
http://brenreyn.blogspot.com
The spammers and script-kiddies have succeeded in making it impossible for
me to use a real e-mail address in public newsgroups. E-mail replies to
this post will be deleted without being read. Any e-mail claiming to be
from brenreyn at indigo dot ie that is not digitally signed by me with a
GlobalSign digital certificate is a forgery and should be deleted without
being read. Follow-up questions should in general be posted to the
newsgroup, but if you have a good reason to send me e-mail, you'll find
a useable e-mail address at the URL above.
"Jon" <jonremovemewest@.msn.com> wrote in message
news:Ode5H%23lcEHA.3716@.TK2MSFTNGP11.phx.gbl...
> There's a thread on microsoft.public.sqlserver.server called "Diagram
Editor
> doesn't work in SQLServer 2000", it says something about a dll conflict
> caused by installation of VB6. I do have VB 6 installed so I wonder if
this
> is the culprit. What do you all think? I'm not fooling with my
registrations
> until I know what's up with this. What do you all have installed? Any
> suggestions.
> Jon
>
|||Well I broke down and sent a support email to MS. Maybe I'll get lucky and
get a good quick response back from them on this one. This thing is driving
me nuts!
Jon

Access/Enterprise Manager Diagrams Incompatible?

I asked this one a while back but I still haven't got it figured out yet.
What my problem boils down to is that SQL server diagrams created with
Access XP (latest version with patches) created through an ADP and diagrams
created with enterprise manager (latest version + patches) seem to be
completely incompatible. Whenever I open a diagram created with one tool in
the other tool, the tool doing the opening crashes, completely crashes at
that. I'm working on a project and the DB is growing to a complexity where I
really need a reliable way to share the diagrams with my team members. I
don't want to put too much work into good diagrams with one tool if they're
going to be useless in the other. Other developers I have spoken with don't
seem to have this problem. Have I missed a patch? Is this a known
incompatibility? Is something configured wrong? I'm at wits end.
Sorry for the cross posting but this anomaly is really annoying me and we
need to use both Enterprise Manager and Access and this is holding us up
somewhat. So I'm hoping to fish for answers in the largest pool. Thanks in
advance to anyone who can give me a clue on this one!
JonI have used both interchangeably without a problem. It would seem a drastic
step to start uninstalling/reinstalling without knowing exactly what the
problem may be or if it will be cured. I suggest just creating and viewing
all the diagrams in Access because everyone should have that installed.
--
Arvin Meyer, MCP, MVP
Microsoft Access
Free Access downloads:
http://www.datastrat.com
http://www.mvps.org/access
"Jon" <jonremovemewest@.msn.com> wrote in message
news:ehiDwrHcEHA.2476@.TK2MSFTNGP09.phx.gbl...
> I asked this one a while back but I still haven't got it figured out yet.
> What my problem boils down to is that SQL server diagrams created with
> Access XP (latest version with patches) created through an ADP and
diagrams
> created with enterprise manager (latest version + patches) seem to be
> completely incompatible. Whenever I open a diagram created with one tool
in
> the other tool, the tool doing the opening crashes, completely crashes at
> that. I'm working on a project and the DB is growing to a complexity where
I
> really need a reliable way to share the diagrams with my team members. I
> don't want to put too much work into good diagrams with one tool if
they're
> going to be useless in the other. Other developers I have spoken with
don't
> seem to have this problem. Have I missed a patch? Is this a known
> incompatibility? Is something configured wrong? I'm at wits end.
> Sorry for the cross posting but this anomaly is really annoying me and we
> need to use both Enterprise Manager and Access and this is holding us up
> somewhat. So I'm hoping to fish for answers in the largest pool. Thanks in
> advance to anyone who can give me a clue on this one!
>
> Jon
>|||Which version of Access do you use? Access2002(XP) or Access2003? Since I
have the same problem with SQL Server2000(Developer edition) and AccessXP,
i.e. Diagram created in one program crashes othe other program when opening.
I just wonder whether Access 2003 has the same problem or not. At least,
with AccessXP, it is not "Just me" thing.
"Arvin Meyer" <a@.m.com> wrote in message
news:ObcInaKcEHA.3480@.TK2MSFTNGP11.phx.gbl...
> I have used both interchangeably without a problem. It would seem a
drastic
> step to start uninstalling/reinstalling without knowing exactly what the
> problem may be or if it will be cured. I suggest just creating and viewing
> all the diagrams in Access because everyone should have that installed.
> --
> Arvin Meyer, MCP, MVP
> Microsoft Access
> Free Access downloads:
> http://www.datastrat.com
> http://www.mvps.org/access
> "Jon" <jonremovemewest@.msn.com> wrote in message
> news:ehiDwrHcEHA.2476@.TK2MSFTNGP09.phx.gbl...
yet.[vbcol=seagreen]
> diagrams
> in
at[vbcol=seagreen]
where[vbcol=seagreen]
> I
> they're
> don't
we[vbcol=seagreen]
in[vbcol=seagreen]
>|||I forgot to mention that the diagram created in Enterprise Manager also
crashes Visual Studio2003, if I try to open it in Server Explorer. So, the
problem seems from Enterprise Manager, rather than AccessXP. As I said, I am
using SQL Server2000 developer edition with SP3.
"Norman Yuan" <nobody@.nowhere.no> wrote in message
news:OyDRGNMcEHA.3476@.tk2msftngp13.phx.gbl...
> Which version of Access do you use? Access2002(XP) or Access2003? Since I
> have the same problem with SQL Server2000(Developer edition) and AccessXP,
> i.e. Diagram created in one program crashes othe other program when
opening.
> I just wonder whether Access 2003 has the same problem or not. At least,
> with AccessXP, it is not "Just me" thing.
>
> "Arvin Meyer" <a@.m.com> wrote in message
> news:ObcInaKcEHA.3480@.TK2MSFTNGP11.phx.gbl...
> drastic
viewing[vbcol=seagreen]
> yet.
tool[vbcol=seagreen]
> at
> where
I[vbcol=seagreen]
> we
up[vbcol=seagreen]
Thanks[vbcol=seagreen]
> in
>|||I'm on Access XP, I also have 2000 installed I bet it would be the same
there though. I'd have to check to be sure. Yeah it looks like some of us
have this problem and some aren't, I'm hoping that someone knows something
as I'm really starting to like ADPs but I need this to work correctly. I
really don't want to go through the whole reinstall rigmarole either as it's
a huge time sink and I have real work to do(plus like you all said there's
no guarantee that it will fix anything).
Jon|||Ditto here on the SQL config...SQL 2000 developer edition with SP3 applied.
Although I tried it with enterprise edition and got the same bad results.
Jon|||There's a thread on microsoft.public.sqlserver.server called "Diagram Editor
doesn't work in SQLServer 2000", it says something about a dll conflict
caused by installation of VB6. I do have VB 6 installed so I wonder if this
is the culprit. What do you all think? I'm not fooling with my registrations
until I know what's up with this. What do you all have installed? Any
suggestions.
Jon|||I don't think there's any question but that it is a DLL conflict, Jon. The
issue is, of course, which DLL, and what to do about it.
I had problems with the diagram editor on my old PC, which had Visual Studio
6 (including VB6) installed. I do not have problems on my new PC, which has
never had Visual Studio 6 installed. So yes, it would seem likely that the
problem DLL is installed by Visual Studio 6. But that doesn't rule out the
possibility that it may also be installed by other applications.
Brendan Reynolds (MVP)
http://brenreyn.blogspot.com
The spammers and script-kiddies have succeeded in making it impossible for
me to use a real e-mail address in public newsgroups. E-mail replies to
this post will be deleted without being read. Any e-mail claiming to be
from brenreyn at indigo dot ie that is not digitally signed by me with a
GlobalSign digital certificate is a forgery and should be deleted without
being read. Follow-up questions should in general be posted to the
newsgroup, but if you have a good reason to send me e-mail, you'll find
a useable e-mail address at the URL above.
"Jon" <jonremovemewest@.msn.com> wrote in message
news:Ode5H%23lcEHA.3716@.TK2MSFTNGP11.phx.gbl...
> There's a thread on microsoft.public.sqlserver.server called "Diagram
Editor
> doesn't work in SQLServer 2000", it says something about a dll conflict
> caused by installation of VB6. I do have VB 6 installed so I wonder if
this
> is the culprit. What do you all think? I'm not fooling with my
registrations
> until I know what's up with this. What do you all have installed? Any
> suggestions.
> Jon
>|||Well I broke down and sent a support email to MS. Maybe I'll get lucky and
get a good quick response back from them on this one. This thing is driving
me nuts!
Jon

Access/Enterprise Manager Diagrams Incompatible?

I asked this one a while back but I still haven't got it figured out yet.
What my problem boils down to is that SQL server diagrams created with
Access XP (latest version with patches) created through an ADP and diagrams
created with enterprise manager (latest version + patches) seem to be
completely incompatible. Whenever I open a diagram created with one tool in
the other tool, the tool doing the opening crashes, completely crashes at
that. I'm working on a project and the DB is growing to a complexity where I
really need a reliable way to share the diagrams with my team members. I
don't want to put too much work into good diagrams with one tool if they're
going to be useless in the other. Other developers I have spoken with don't
seem to have this problem. Have I missed a patch? Is this a known
incompatibility? Is something configured wrong? I'm at wits end.
Sorry for the cross posting but this anomaly is really annoying me and we
need to use both Enterprise Manager and Access and this is holding us up
somewhat. So I'm hoping to fish for answers in the largest pool. Thanks in
advance to anyone who can give me a clue on this one!
JonI have used both interchangeably without a problem. It would seem a drastic
step to start uninstalling/reinstalling without knowing exactly what the
problem may be or if it will be cured. I suggest just creating and viewing
all the diagrams in Access because everyone should have that installed.
--
Arvin Meyer, MCP, MVP
Microsoft Access
Free Access downloads:
http://www.datastrat.com
http://www.mvps.org/access
"Jon" <jonremovemewest@.msn.com> wrote in message
news:ehiDwrHcEHA.2476@.TK2MSFTNGP09.phx.gbl...
> I asked this one a while back but I still haven't got it figured out yet.
> What my problem boils down to is that SQL server diagrams created with
> Access XP (latest version with patches) created through an ADP and
diagrams
> created with enterprise manager (latest version + patches) seem to be
> completely incompatible. Whenever I open a diagram created with one tool
in
> the other tool, the tool doing the opening crashes, completely crashes at
> that. I'm working on a project and the DB is growing to a complexity where
I
> really need a reliable way to share the diagrams with my team members. I
> don't want to put too much work into good diagrams with one tool if
they're
> going to be useless in the other. Other developers I have spoken with
don't
> seem to have this problem. Have I missed a patch? Is this a known
> incompatibility? Is something configured wrong? I'm at wits end.
> Sorry for the cross posting but this anomaly is really annoying me and we
> need to use both Enterprise Manager and Access and this is holding us up
> somewhat. So I'm hoping to fish for answers in the largest pool. Thanks in
> advance to anyone who can give me a clue on this one!
>
> Jon
>|||Which version of Access do you use? Access2002(XP) or Access2003? Since I
have the same problem with SQL Server2000(Developer edition) and AccessXP,
i.e. Diagram created in one program crashes othe other program when opening.
I just wonder whether Access 2003 has the same problem or not. At least,
with AccessXP, it is not "Just me" thing.
"Arvin Meyer" <a@.m.com> wrote in message
news:ObcInaKcEHA.3480@.TK2MSFTNGP11.phx.gbl...
> I have used both interchangeably without a problem. It would seem a
drastic
> step to start uninstalling/reinstalling without knowing exactly what the
> problem may be or if it will be cured. I suggest just creating and viewing
> all the diagrams in Access because everyone should have that installed.
> --
> Arvin Meyer, MCP, MVP
> Microsoft Access
> Free Access downloads:
> http://www.datastrat.com
> http://www.mvps.org/access
> "Jon" <jonremovemewest@.msn.com> wrote in message
> news:ehiDwrHcEHA.2476@.TK2MSFTNGP09.phx.gbl...
> > I asked this one a while back but I still haven't got it figured out
yet.
> > What my problem boils down to is that SQL server diagrams created with
> > Access XP (latest version with patches) created through an ADP and
> diagrams
> > created with enterprise manager (latest version + patches) seem to be
> > completely incompatible. Whenever I open a diagram created with one tool
> in
> > the other tool, the tool doing the opening crashes, completely crashes
at
> > that. I'm working on a project and the DB is growing to a complexity
where
> I
> > really need a reliable way to share the diagrams with my team members. I
> > don't want to put too much work into good diagrams with one tool if
> they're
> > going to be useless in the other. Other developers I have spoken with
> don't
> > seem to have this problem. Have I missed a patch? Is this a known
> > incompatibility? Is something configured wrong? I'm at wits end.
> >
> > Sorry for the cross posting but this anomaly is really annoying me and
we
> > need to use both Enterprise Manager and Access and this is holding us up
> > somewhat. So I'm hoping to fish for answers in the largest pool. Thanks
in
> > advance to anyone who can give me a clue on this one!
> >
> >
> > Jon
> >
> >
>|||I forgot to mention that the diagram created in Enterprise Manager also
crashes Visual Studio2003, if I try to open it in Server Explorer. So, the
problem seems from Enterprise Manager, rather than AccessXP. As I said, I am
using SQL Server2000 developer edition with SP3.
"Norman Yuan" <nobody@.nowhere.no> wrote in message
news:OyDRGNMcEHA.3476@.tk2msftngp13.phx.gbl...
> Which version of Access do you use? Access2002(XP) or Access2003? Since I
> have the same problem with SQL Server2000(Developer edition) and AccessXP,
> i.e. Diagram created in one program crashes othe other program when
opening.
> I just wonder whether Access 2003 has the same problem or not. At least,
> with AccessXP, it is not "Just me" thing.
>
> "Arvin Meyer" <a@.m.com> wrote in message
> news:ObcInaKcEHA.3480@.TK2MSFTNGP11.phx.gbl...
> > I have used both interchangeably without a problem. It would seem a
> drastic
> > step to start uninstalling/reinstalling without knowing exactly what the
> > problem may be or if it will be cured. I suggest just creating and
viewing
> > all the diagrams in Access because everyone should have that installed.
> > --
> > Arvin Meyer, MCP, MVP
> > Microsoft Access
> > Free Access downloads:
> > http://www.datastrat.com
> > http://www.mvps.org/access
> >
> > "Jon" <jonremovemewest@.msn.com> wrote in message
> > news:ehiDwrHcEHA.2476@.TK2MSFTNGP09.phx.gbl...
> > > I asked this one a while back but I still haven't got it figured out
> yet.
> > > What my problem boils down to is that SQL server diagrams created with
> > > Access XP (latest version with patches) created through an ADP and
> > diagrams
> > > created with enterprise manager (latest version + patches) seem to be
> > > completely incompatible. Whenever I open a diagram created with one
tool
> > in
> > > the other tool, the tool doing the opening crashes, completely crashes
> at
> > > that. I'm working on a project and the DB is growing to a complexity
> where
> > I
> > > really need a reliable way to share the diagrams with my team members.
I
> > > don't want to put too much work into good diagrams with one tool if
> > they're
> > > going to be useless in the other. Other developers I have spoken with
> > don't
> > > seem to have this problem. Have I missed a patch? Is this a known
> > > incompatibility? Is something configured wrong? I'm at wits end.
> > >
> > > Sorry for the cross posting but this anomaly is really annoying me and
> we
> > > need to use both Enterprise Manager and Access and this is holding us
up
> > > somewhat. So I'm hoping to fish for answers in the largest pool.
Thanks
> in
> > > advance to anyone who can give me a clue on this one!
> > >
> > >
> > > Jon
> > >
> > >
> >
> >
>|||I'm on Access XP, I also have 2000 installed I bet it would be the same
there though. I'd have to check to be sure. Yeah it looks like some of us
have this problem and some aren't, I'm hoping that someone knows something
as I'm really starting to like ADPs but I need this to work correctly. I
really don't want to go through the whole reinstall rigmarole either as it's
a huge time sink and I have real work to do(plus like you all said there's
no guarantee that it will fix anything).
Jon|||Ditto here on the SQL config...SQL 2000 developer edition with SP3 applied.
Although I tried it with enterprise edition and got the same bad results.
Jon|||There's a thread on microsoft.public.sqlserver.server called "Diagram Editor
doesn't work in SQLServer 2000", it says something about a dll conflict
caused by installation of VB6. I do have VB 6 installed so I wonder if this
is the culprit. What do you all think? I'm not fooling with my registrations
until I know what's up with this. What do you all have installed? Any
suggestions.
Jon|||I don't think there's any question but that it is a DLL conflict, Jon. The
issue is, of course, which DLL, and what to do about it.
I had problems with the diagram editor on my old PC, which had Visual Studio
6 (including VB6) installed. I do not have problems on my new PC, which has
never had Visual Studio 6 installed. So yes, it would seem likely that the
problem DLL is installed by Visual Studio 6. But that doesn't rule out the
possibility that it may also be installed by other applications.
--
Brendan Reynolds (MVP)
http://brenreyn.blogspot.com
The spammers and script-kiddies have succeeded in making it impossible for
me to use a real e-mail address in public newsgroups. E-mail replies to
this post will be deleted without being read. Any e-mail claiming to be
from brenreyn at indigo dot ie that is not digitally signed by me with a
GlobalSign digital certificate is a forgery and should be deleted without
being read. Follow-up questions should in general be posted to the
newsgroup, but if you have a good reason to send me e-mail, you'll find
a useable e-mail address at the URL above.
"Jon" <jonremovemewest@.msn.com> wrote in message
news:Ode5H%23lcEHA.3716@.TK2MSFTNGP11.phx.gbl...
> There's a thread on microsoft.public.sqlserver.server called "Diagram
Editor
> doesn't work in SQLServer 2000", it says something about a dll conflict
> caused by installation of VB6. I do have VB 6 installed so I wonder if
this
> is the culprit. What do you all think? I'm not fooling with my
registrations
> until I know what's up with this. What do you all have installed? Any
> suggestions.
> Jon
>|||Well I broke down and sent a support email to MS. Maybe I'll get lucky and
get a good quick response back from them on this one. This thing is driving
me nuts!
Jon

Access report with SQL server BE hangs on one p/c but not others

Hi
I have a MS Access database which uses SQL server 2000 (SBS 2003) as a
back end (using ODBC).
Can anybody explain to me why one p/c should have a problem with one
report? When you click on the button which runs the report, the egg
timer comes on for about 10 minutes and then the following error is
displayed:
Connection failed
SQL State '01000'
SQL Server error 53
[microsoft][ODBC SQL Server Driver][DBNETLIB]Connection Open
Connection failed
SQL State '08001
SQL Error 17
[microsoft][ODBC SQL Server Driver][DBNETLIB]SQL Server does not exist
or access denied
All other reports in the Access application run fine on this p/c. The
report itself runs fine on all other p/cs that I have tried it on. The
same error occurs whichever user is logged onto the p/c.
Can anybody make any suggestions as to what might be going on?
Thanks
ColinBooby
At first glance it seems that this specific report is connected to SQL
Server with 'wrong' login or to 'wrong' database. Also it could permission
issues
Can you compare everything with 'working' reports?
"Bobby" <bobby2@.blueyonder.co.uk> wrote in message
news:1180954455.134604.78650@.w5g2000hsg.googlegroups.com...
> Hi
> I have a MS Access database which uses SQL server 2000 (SBS 2003) as a
> back end (using ODBC).
> Can anybody explain to me why one p/c should have a problem with one
> report? When you click on the button which runs the report, the egg
> timer comes on for about 10 minutes and then the following error is
> displayed:
> Connection failed
> SQL State '01000'
> SQL Server error 53
> [microsoft][ODBC SQL Server Driver][DBNETLIB]Connection Open
> Connection failed
> SQL State '08001
> SQL Error 17
> [microsoft][ODBC SQL Server Driver][DBNETLIB]SQL Server does not exist
> or access denied
> All other reports in the Access application run fine on this p/c. The
> report itself runs fine on all other p/cs that I have tried it on. The
> same error occurs whichever user is logged onto the p/c.
> Can anybody make any suggestions as to what might be going on?
> Thanks
> Colin
>

Access Front End and SQL Server 2000 Record Level Access Control

Hello,

We are using Access ADP as a front end, SQL Server 2000 as a back end.
We have a customer contact database. We would like to limit certain
users to only receive certain records based on Windows NT group
membership.

For example, Eastern Sales Group can see clients located in their
region, but they cannot see clients located in the Northern Region.

Is there an elegant way to do this? Below a two solutions which have
been proposed, but none seem to fit. Access is required as a Front End
for its ease of use.

*********
** 1 **
*********
Add an additional attribute (bit mask value) to tblCustomers, and
query appropriately based on the user's group membership.

Problem:
Access allows users direct access to the underlying table.

*********
** 2 **
*********
Create a separe table for each group (effectively splitting
tblCustomers into smaller, separate tables based on group access).
Then, apply SQL Server security on the objects to enforce the business
rules.

Problem:
Does this break Normal Form? I've never seen a solution like this.

I've googled and found similar questions, but not a good solution.

Any suggestions would be appreciated.

Thanks,
Jeff
Jeffrey Walton
noloader.at.yahoo.com"Noloader" <noloader@.yahoo.com> wrote in message
news:6b543aa7.0404231447.777fe29c@.posting.google.c om...
> Hello,
> We are using Access ADP as a front end, SQL Server 2000 as a back end.
> We have a customer contact database. We would like to limit certain
> users to only receive certain records based on Windows NT group
> membership.
> For example, Eastern Sales Group can see clients located in their
> region, but they cannot see clients located in the Northern Region.
> Is there an elegant way to do this? Below a two solutions which have
> been proposed, but none seem to fit. Access is required as a Front End
> for its ease of use.
> *********
> ** 1 **
> *********
> Add an additional attribute (bit mask value) to tblCustomers, and
> query appropriately based on the user's group membership.
> Problem:
> Access allows users direct access to the underlying table.
> *********
> ** 2 **
> *********
> Create a separe table for each group (effectively splitting
> tblCustomers into smaller, separate tables based on group access).
> Then, apply SQL Server security on the objects to enforce the business
> rules.
> Problem:
> Does this break Normal Form? I've never seen a solution like this.
> I've googled and found similar questions, but not a good solution.
> Any suggestions would be appreciated.
> Thanks,
> Jeff
> Jeffrey Walton
> noloader.at.yahoo.com

In general, there is no reason why your users should need to access tables
directly. If you manage data access through stored procedures, then the
procedures can check role membership and only return or update those rows
which are permitted to the user. You could also use views, based on role
membership, or use application roles and handle everything in the client
application.

I would avoid solution 2, because it duplicates data - whatever information
you use to partition the data could also be put in a column. But if you have
a large amount of data, and if users only access their own data, then this
might also be an option.

Simon|||RE/
>We have a customer contact database. We would like to limit certain
>users to only receive certain records based on Windows NT group
>membership.

Based on what little experience I've had doing an Access front end against SQL
Server, I'd set SQL Server security so that nobody and nothing can get directly
to the tables in question and then develop stored procedures and/or views to
move the data back-and-forth between tables and app.
--
PeteCresswell