By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
424,652 Members | 1,995 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 424,652 IT Pros & Developers. It's quick & easy.

Preventing an ADB Auto-Start

P: n/a
I'm working for the first time on an existing application that
communicates with an SQL Server database. We've backed up the database
and installed it on our own machine, and copied the ADB file to our
PCs.

One problem. We can't open up the ADB file. When clicked, with the
shift key down or not, it spends a long time in hourglass mode, and has
to be stopped via the task manager.

I don't know why it is ignoring the shift key (does this feature not
hold true for ADB files?), but I can guess that it is hanging because
it is not finding the SQL Server database in it's expected location.
Changing the location was of course the first thing I was going to
change in the code once I opened up the ADB file.

Moving the SQL Database to an expected location is not an option (and
probably wouldn't get me to my goal of opening up the ADB file to begin
with). What am I missing when it comes to opening up ADB files? I
don't seem to be able to find the correct key words for Google to find
the answer.

Thanks,
-john

Dec 14 '06 #1
Share this Question
Share on Google+
4 Replies


P: n/a
On 14 Dec 2006 12:07:24 -0800, jg*****@ripco.com wrote:

Works just fine with the NorthwindCS sample application. What's
different with yours?

-Tom.

>I'm working for the first time on an existing application that
communicates with an SQL Server database. We've backed up the database
and installed it on our own machine, and copied the ADB file to our
PCs.

One problem. We can't open up the ADB file. When clicked, with the
shift key down or not, it spends a long time in hourglass mode, and has
to be stopped via the task manager.

I don't know why it is ignoring the shift key (does this feature not
hold true for ADB files?), but I can guess that it is hanging because
it is not finding the SQL Server database in it's expected location.
Changing the location was of course the first thing I was going to
change in the code once I opened up the ADB file.

Moving the SQL Database to an expected location is not an option (and
probably wouldn't get me to my goal of opening up the ADB file to begin
with). What am I missing when it comes to opening up ADB files? I
don't seem to be able to find the correct key words for Google to find
the answer.

Thanks,
-john
Dec 15 '06 #2

P: n/a

Tom van Stiphout wrote:
On 14 Dec 2006 12:07:24 -0800, jg*****@ripco.com wrote:

Works just fine with the NorthwindCS sample application. What's
different with yours?
Well, if I could open it up, I could tell. Unfortunately...

So you're just performing the shift key trick? Nothing else?

Thanks,
-john

Dec 15 '06 #3

P: n/a

Tom van Stiphout wrote:
On 14 Dec 2006 12:07:24 -0800, jg*****@ripco.com wrote:

Works just fine with the NorthwindCS sample application. What's
different with yours?

-Tom.
Semi-found out the problem. After a set of difficulties that I won't
bore you with, I managed to get to the client's machine and run the
application from there. I found that the timeout setting for the
connection was set to 65465 seconds (that's over 18 hours) and
apparently an ADB application is going to try that regardless of
whether you've held down the shift key or not.

I made a new copy of of the file, with the connection property changed
with a timeout of 30 seconds. I can open up the application now.

Although oddly enough, I don't see an AutoStart macro. Is there
another way to auto-start?

Thanks,
-john

Dec 15 '06 #4

P: n/a
On 15 Dec 2006 15:00:35 -0800, jg*****@ripco.com wrote:

Either an AutoExec macro, or a Startup form (Tools Startup)

-Tom.

>
Tom van Stiphout wrote:
>On 14 Dec 2006 12:07:24 -0800, jg*****@ripco.com wrote:

Works just fine with the NorthwindCS sample application. What's
different with yours?

-Tom.

Semi-found out the problem. After a set of difficulties that I won't
bore you with, I managed to get to the client's machine and run the
application from there. I found that the timeout setting for the
connection was set to 65465 seconds (that's over 18 hours) and
apparently an ADB application is going to try that regardless of
whether you've held down the shift key or not.

I made a new copy of of the file, with the connection property changed
with a timeout of 30 seconds. I can open up the application now.

Although oddly enough, I don't see an AutoStart macro. Is there
another way to auto-start?

Thanks,
-john
Dec 16 '06 #5

This discussion thread is closed

Replies have been disabled for this discussion.