Please can someone help me get my ultradev on the mac to work. Ive had it for 3 months now and am gettin so frustrated with the dam thing. All i want is to be able to get a DSN connection, I know i have to do it remotely but it just doesnt want to work.....its driving me mad - please help

Hi Ray,

I empathize with your frustration. To be able to help you, one needs a bit more information. Can you provide more details as to the database type, driver/provider, and the whole connection string you are using? It might be helpful to know how you have defined your site in UltraDev as well (as to your application server, whether or not you are using ASP, Cold Fusion, Java, etc.)
To encourage you, I can tell you that you do have a solvable problem. <img src=../images/dmxzone/forum/icon_smile.gif border=0 align=middle> Do hang in there-it will get easier.

Jean-Marie

Thank god someone can help <img src=../images/dmxzone/forum/icon_smile.gif border=0 align=middle>

Right let me answer this as best as I can....
Ok the database is done in access, on a virtual pc, im tryin to use ASP. Now i'm not using PWS or IIs cos (as I asume) I cannot connect through a local server, well unless i hook up a pc to the mac defying the whole ultradev on mac in the first place.
And im a bit lost when u say "how ive defined my site in ultradev........if configured the define site as usual, and connected the ftp to the right place, but as soon as i go to hit that dam DSN button the errors appear

do I need odbc access on my remote server?????

Ray

see, now im outta my depth <img src=../images/dmxzone/forum/icon_smile_wink.gif border=0 align=middle>

Hi Ray,

Thanks for the additional info Ray. I hope the following may be helpful to you.
A. First of all, the key to a successful database connection from a Macintosh to a remote server is the Site Definition dialog box, thus the questions about how you have "defined your site."
I will assume that you are using UltraDev 4 and will be connecting to a Windows 2000/NT remote server that is able to host your Access database and allows you to set up a DSN on their server. Please correct my assumptions if I'm wrong. To set up your connection, you will have to be connected to the internet and have access to your remote/application server.

When defining your site, the Application Server dialog box in the Site Definitions area has to be filled out properly to connect to your remote application server. You need to define the following items since you will be using FTP to connect:
1. Server Model: ASP
2. Default Scripting Language: VBScript OR Javascript(JScript), whichever you are using.
3.Default Page Extension: .asp
4.Server Access: FTP
5.Host Directory: The directory on the application server that hosts your web site--where documents visible to the public are stored; for example, if your website host directory is called MyTutorialSite, then you'd put MyTutorialSite/
6.Login: Your username for the FTP setting.
7.Password: Your password.
8. URL Prefix: The IP address and path to your site; this is the key ingredient to a successful connection. (For example, if your site is located at MyDomainName/MyTutorialSite, then that's exactly where the URL prefix should be pointing.)
...*To be continued*...

...Continued, Part 2

B. I am also assuming that you have already copied your Access database file to the server so that you know it's location. If not, you will need to do so. Additionally, if you plan on connecting to your database using a DSN, this will need to be set up on your *Remote* server according to your specific webhost's directions. When you set up the DSN, give it a name and point it to the database that you copied to the server (In addition, make sure the database directory has the proper permissions set).

C. Click OK.

D. Click Done.

E. In the site window(Site&gt;Files), click the Connect button to view the remote site and then verify that you've specified the correct folder on the remote site before you upload your files. At this point, you can select all the files under the local folder that you want to upload, including the images folder, and click the blue up-arrow on the toolbar to upload them to the remote site or can manually copy them to their proper directories on the remote site.
*...to be continued...

...Continued, Part 3

F. Now to create the actual database connection!
1. In UltraDev, choose Connections from the Modify menu. The Connections dialog box appears.
2. Click the New button and select Data Source Name(DSN) from the pop-up menu. The Data Source Name(DSN) dialog box appears.
3. Enter a name for the new connection. Make it something descriptive of what the connection is used for, and keep it simple. You can prefix it with "conn". For example: connName (the "conn" before the Name helps you to distinguish the connection from other objects in your code).
4. In the Data Source Name(DSN) box, enter the *same* Data Source Name that you defined on your remote server.
5. Where it says UltraDev Should Connect, choose *Using DSN on the Application Server.* (This is the only choice for Macintosh users).
6. Click test.
UltraDev attempts to connect to the database (you might want to make sure you have some sort of data in the fields). If the connection fails, double-check the DSN. If the connection still fails, check your URL prefix for the application server.
7. Click OK. Your new connection should now appear in the Connections dialog box.
8. Click Done to close the Connections dialog box.

Now you should be ready to go. <img src=../images/dmxzone/forum/icon_smile.gif border=0 align=middle>

If you decide you want to use a DSN-less connection instead of a DSN, I can help you with the connection string. I usually connect to Access using a DSN-less OLEDB connection (Provider=Microsoft.Jet.OLEDB4.0) using Server.MapPath, and it's really not that hard to set up. I think it's easier and less hassle than setting a DSN is. Then you don't have to bother with setting up a DSN on your remote server, the Server.MapPath generates a proper file path to the database, and studies show such a connection to be faster and more stable.

With warm regards,

Jean-Marie

<BLOCKQUOTE id=quote><font size=1 face="Verdana, Arial, Helvetica" id=quote>quote:<hr height=1 noshade id=quote>
...Continued, Part 3

F. Now to create the actual database connection!
1. In UltraDev, choose Connections from the Modify menu. The Connections dialog box appears.
2. Click the New button and select Data Source Name(DSN) from the pop-up menu. The Data Source Name(DSN) dialog box appears.
3. Enter a name for the new connection. Make it something descriptive of what the connection is used for, and keep it simple. You can prefix it with "conn". For example: connName (the "conn" before the Name helps you to distinguish the connection from other objects in your code).
4. In the Data Source Name(DSN) box, enter the *same* Data Source Name that you defined on your remote server.
5. Where it says UltraDev Should Connect, choose *Using DSN on the Application Server.* (This is the only choice for Macintosh users).
6. Click test.
UltraDev attempts to connect to the database (you might want to make sure you have some sort of data in the fields). If the connection fails, double-check the DSN. If the connection still fails, check your URL prefix for the application server.
7. Click OK. Your new connection should now appear in the Connections dialog box.
8. Click Done to close the Connections dialog box.

Now you should be ready to go. <img src=../images/dmxzone/forum/icon_smile.gif border=0 align=middle>

If you decide you want to use a DSN-less connection instead of a DSN, I can help you with the connection string. I usually connect to Access using a DSN-less OLEDB connection (Provider=Microsoft.Jet.OLEDB4.0) using Server.MapPath, and it's really not that hard to set up. I think it's easier and less hassle than setting a DSN is. Then you don't have to bother with setting up a DSN on your remote server, the Server.MapPath generates a proper file path to the database, and studies show such a connection to be faster and more stable.

With warm regards,

Jean-Marie
<hr height=1 noshade id=quote></BLOCKQUOTE id=quote></font id=quote><font face="Verdana, Arial, Helvetica" size=2 id=quote>

<BLOCKQUOTE id=quote><font size=1 face="Verdana, Arial, Helvetica" id=quote>quote:<hr height=1 noshade id=quote>
...Continued, Part 3

F. Now to create the actual database connection!
1. In UltraDev, choose Connections from the Modify menu. The Connections dialog box appears.
2. Click the New button and select Data Source Name(DSN) from the pop-up menu. The Data Source Name(DSN) dialog box appears.
3. Enter a name for the new connection. Make it something descriptive of what the connection is used for, and keep it simple. You can prefix it with "conn". For example: connName (the "conn" before the Name helps you to distinguish the connection from other objects in your code).
4. In the Data Source Name(DSN) box, enter the *same* Data Source Name that you defined on your remote server.
5. Where it says UltraDev Should Connect, choose *Using DSN on the Application Server.* (This is the only choice for Macintosh users).
6. Click test.
UltraDev attempts to connect to the database (you might want to make sure you have some sort of data in the fields). If the connection fails, double-check the DSN. If the connection still fails, check your URL prefix for the application server.
7. Click OK. Your new connection should now appear in the Connections dialog box.
8. Click Done to close the Connections dialog box.

Now you should be ready to go. <img src=../images/dmxzone/forum/icon_smile.gif border=0 align=middle>

If you decide you want to use a DSN-less connection instead of a DSN, I can help you with the connection string. I usually connect to Access using a DSN-less OLEDB connection (Provider=Microsoft.Jet.OLEDB4.0) using Server.MapPath, and it's really not that hard to set up. I think it's easier and less hassle than setting a DSN is. Then you don't have to bother with setting up a DSN on your remote server, the Server.MapPath generates a proper file path to the database, and studies show such a connection to be faster and more stable.

With warm regards,

Jean-Marie
<hr height=1 noshade id=quote></BLOCKQUOTE id=quote></font id=quote><font face="Verdana, Arial, Helvetica" size=2 id=quote>

Hi Jean-Marie,

thanks for your helpful assistence on the setup of a Mac UD site definition. I have had a similar nightmare in trying to get things to work.

I have managed to setup my Win2k machine with IIS as my server connected to my network and have entered the details of the ip address of the server machine. I have selected the folder on the remote machine but when I click the connect button I get an error stating the folder can't be found? The connection apart from that works, ie; the green light comes on in the connection icon button.

Same error when trying to get the server connection. Any clues to why this might be happening?

have u turned on pws????? personal web manager?

i take it ur running a fat32 system?

have u got the folder/directories u wish to look at in the wwwroot folder?

c: inetpub\wwwroot
then enable pws, and go to TheNameOfYourComputer/TheNameOfTheDirectoryYouWishToBrowse

if not get back to me and ill trouble shoot again

Ray