Newbie: missing something fundamental

[Tom Kemp]

I have an .adp file which I have converted to .ade and compiled into a
Runtime version with Windows XP Microsoft Office Developer. I have developed
a SQL Server 2000 backend database and on my computer they talk together
nicely.

When I deploy this stuff, how do I tell each .ade file where it now has to
look to find the deployed database? They're like little children who won't
leave home, always looking for the original server with which they were
developed.

I can't expect my client to use an .adp file and shift-open it then use the
File -> Connection menu to find the right server, especially if this has to
be done for every instance of the front end application.

What am I missing?

Thanks,
Tom

 

[Robert Morley]

Assuming that your SQL Server is centralized, before you release your final
version, point your ADP/ADE to the deployed database instead of your local
database, then release it.

Or am I misunderstanding?



Rob

 

[giorgio rancati]

Hi Tom,

 

[Tom Kemp]

Thanks, Rob,

the .ade file is a prototype of something more robust I'm designing. It's a
way of capturing users' true expectations of the system so there are
frequent iterations and I want to make it as easy for them

Assume my clients don't have MS Access and I am distributing a runtime
version for them to deploy to each PC which will use the prototype. I'm
looking for a way of telling the .ade the name of my client's server
_before_ I send it off to them for deployment in their organization.

Or do I have to ask their IT department hook the .ade file up to their
server and then distribute that copy?

Best wishes,
Tom

 

[Robert Morley]

What you're looking for then is:

Application.CurrentProject.OpenConnection

You can look it up in the help file for the parameters, but basically it
lets you connect the current project to a different server.



Rob