.ade runtime - SQL Connection issue

[Guest]

Hi,

I have packaged up an .ade project. Everything installs OK and when the
Splash screen opens the project tries to connect to a SQL server and then
fails - this OK. I was using a button to open the SQL Connection dialog in
the .adp project (which worked fine), but with the .ade/runtime version I
have no such luck. Therefore I can't change the SQL Connection and connect
the project to a local SQL Server.

The SQL Connection button I use is:

Private Sub btnChangeConn_Click()
DoCmd.RunCommand acCmdConnection
End Sub

Should I be including more code with this function? or is there someother
way to do it?

Thanks in advance.

 

[Wei Lu]

Hi Alan,

Thank you for your post.

Would you pleae send the ade project to me for troubleshooting?

You may zip the file and send to me directly. I understand the information
may be sensitive to you, my direct email address is
(e-mail address removed) ( Please remove the ONLINE when you send the
email ), you may send the file to me directly and I will keep it secure.

Sincerely,

Wei Lu
Microsoft Online Community Support

==================================================

When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.

==================================================
This posting is provided "AS IS" with no warranties, and confers no rights.

 

[Vadim Rapp]

Offshored Microsoft support employees, I understand, get some points for
participating in support newsgroups, so from time to time they come here and
pretend that they could and would help.

In fact, if there was indeed an intention to help, they could spend 5
minutes on recreating the problem on their side, so they would see that this
is indeed the intended behaviour of Access Runtime, and there's nothing to
"troubleshoot". That dialog is part of the "design" functionality, so
Runtime blocks it.

Wei Lu, please note and tell others that next time you guys pretend to be
helping in these newsgroups by posting irrelevant articles, your posts will
be forwarded to the upper levels of Microsoft, with the comments.

If you just want to score some points, please do it elsewhere.


Vadim Rapp

 

[Wei Lu]

Hi Alan,

Based on my further research, I found this issue is by design.

Here are the known workarounds:
1. Use code in the following Knowledge Base article and prompt the user for
server, database, etc. to populate the connection string:


306881 How to Programmatically Change the Connection of a Microsoft Access
http://support.microsoft.com/?id=306881

2. Use a combination of the article above and the following article:

286189 HOWTO: Invoke the OLE DB Data Link Properties Dialog Box in Visual
Basic
http://support.microsoft.com/?id=286189

Hope this will be helpful!

Thank you!

Sincerely,

Wei Lu
Microsoft Online Community Support

==================================================

When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.

==================================================
This posting is provided "AS IS" with no warranties, and confers no rights.

 

[Yan-Hong Huang[MSFT]]

Hello Vadim,

This is Yanhong, manager of MSDN newsgroup support team. I reviewed the
issue thread and discussed with Wei. Wei performed research on it and found
that it looks similar to one reported issue before. Our suppor team did
provide some workaround for that issue and submitted design change.

However, before we post out the workaround here, we want to make sure they
are the same issue so that it won't waste Alan's effort. That is why Wei
asked for a repro sample.

Anyway, Alan, if the problem can't be resolved or you have any more
concerns, please feel free to reply here and we will follow up.

Thanks very much.

Sincerely,
Yanhong Huang
Microsoft Online Community Support

==================================================
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
==================================================

This posting is provided "AS IS" with no warranties, and confers no rights.

 

[david epsom dot com dot au]

I can't help but wonder: are the people designing Access
as ignorant about the product as the occasional posters
we see from MS Support?

If MS was forced to support Access by the absence of MVP's,
would it influence product design?

(david)

 

[Vadim Rapp]

Hello david,
You wrote in conference microsoft.public.access.adp.sqlserver on Wed, 14
Jun 2006 18:48:48 +1000:

ded> I can't help but wonder: are the people designing Access
ded> as ignorant about the product as the occasional posters
ded> we see from MS Support?

ded> If MS was forced to support Access by the absence of MVP's,
ded> would it influence product design?

I think we should better understand how support works.

There's major offshoring company like Infosys. I may be wrong, but I imagine
that someone sitting there and providing support for ms access with his
right hand, very well can at the same resolve billing issues for Aetna
Insurance, while talking on the phone with someone seeking support from Dell
regarding bad colors on the monitor. He/she has received some 2 hours each
training on these matters, then was provided with the address
support.microsoft.com to look into, and some scripts with polite corporate speak:
"thank you for choosing microsoft. We understand how frustrating this
problem is for you, so be assured we will make our best to help. <5 words of
variable information> Thank you for being valued Microsoft customer".
Similar toolsets were provided by Aetna and Dell.

He also had been informed that his "rating" will be raised if he
participates on these newsgroups. So they go post, then probably fill some
report about this achievement.

They are paid their $5/day; while Microsoft probably is paying to Infosys
either hourly ($20-40 / hour), or, more likely, per incident. I noticed that
this support happily waives the per-incident support fees if asked - Infosys
gets their fee per incident, so why care about the "client" (Microsoft).

The main purpose of this circus is not even saving money, but rather
producing rosy reports to shareholders about saving money, which allows
boosting CEO's salary:

http://blogs.zdnet.com/BTL/index.php?p=420

"A new report finds that average CEO compensation at the 50 firms
outsourcing the most service jobs abroad increased by 46 percent in 2003.
CEOs at the 365 large companies surveyed by Business Week only saw an
average raise of 9 percent, according to the report from the Institute for
Policy Studies and United for a Fair Economy, two groups concerned with
economic inequality. The report also found that the ratio of CEO pay to
worker pay reached 301:1 in 2003, up from 282:1 in 2002."


That's how it works.

Vadim Rapp

 

[david epsom dot com dot au]

! gosh !

I'd wondered about offshoring:
http://groups.google.com.au/group/microsoft.public.access/browse_frm/thread/6398822665cd1162

But I'd always imagined that the MS Support people we
see here were some kind of MS employees.

Perhaps it's the kind of secret you have to read about
in the business press ;~/

(david)

 

[aaron.kempf]

I just think that MS does a horrible job of choosing MVP.

they all have to dress the same and think the same.. talk the same

why aren't there any ADP Nationalist MVPs?

BECAUSE MS FOLLOWS GROUPTHINK