Dear Robert:
I am specifically NOT doing this server side. Not that your suggestion might not work.
If there were multiple instances of the same Access front end on a computer, would each have it's own connection. I think so.
But how would it be better? Any simple thing, like a number, that is guaranteed to be unique to an instance of the front end, would work. The hWnd of the initial form would be such a value. You would have to compound that with the Computer Network Name to be universally unique.
Now the SPID would be universally unique by itself. If it were not valuable to know the Network Computer Name (as I have found it to be) then, when I think of it, the SPID would be better. But knowing the Computer Network Name is diagnostic for me when things created "temporarily" get orphaned. The design for me has been to remove them when finished. A system crash or crash of the front end sometimes orphans them. Being able to identify problems with this happening has been useful, so the Network Computer Name is a good thing to know.
Your thinking here is good. My experience leads me to prefer what I have described, but you certainly have the right idea.
Tom Ellison
"Robert Morley" <rmorley[ at ]magma.ca.N0.Freak1n.sparn> wrote in message news:OJnf0cMOGHA.1832[ at ]TK2MSFTNGP11.phx.gbl...
[Quoted Text] >> For an "instance key" I save the hWnd of the initial form. > > If you're doing this server-side, wouldn't [ at ][ at ]SPID be a better choice? Or > is there some problem with that that I'm unaware of? I'm still relatively > new to SQL Server (about a year). > > > > Thanks, > Rob >
|