DataAssist is VERY slow on a very nice machine...??

I've always had problems with DataAssist on any machine I've owned being very slow. The machine I'm on now there's no excuse. I'm on a dual quad-core (8 cores) with 16gb ram. DataAssist still, though, is extremely slow so apparently there's something else causing it.

My test server is here in-house so in Dreamweaver I set up my testing server as Local/Network and I use a mapped network drive to connect to the test server directory. MySQL is on the same test server.

Say I have a bunch of data I want to manage and I'd like to use DataAssist to do it. Well, I start the wizard and it starts connecting to MySQL to check out the tables and everything I guess and this process literally takes about 10 - 15 min before I can move on. to the next step. Once it finally does move on to the next step everything seems to run smoothly but this first step, initially loading the wizard, always takes a very long time. I have to start it and then keep myself occupied elsewhere until it's done ready for me to continue.

I've always just dealt with it but it's becoming very annoying and I'd really like to get this problem resolved. Any info would be greatly appreciated. Thanks!

Try referencing it by ip instead of mapping it.

For example:
\\192.168.1.1\webroot\

Do you mean in the Testing server folder field? Right now it shows the mapped drive: W:\webroot

When I switch to \\1921.68.1.15\webroot I end up with an error message when trying to connect to the test server, the remote folder cannot be accessed or doesn't exist.

\\1921.68.1.15\

That isn't a valid address. try:

\\192.168.1.15\

that was just a typo here. using that sort of path doesn't seem to work in DW CS4. It wants a drive letter. Switching it back to the mapped drive letter makes it work again and everything works great except for DataAssist.

you forgot to put the http: in front of the address. Basically it's the same as any other URL only you are using a local IP address.

Assuming your local server has an ip address of 192.168.1.15 try:
http:\\192.168.1.15\

add the name of the folder for the website (if any) to the end.

Make sure the address is right by typing it into your browser.

I'm talking about the Testing server folder field. You must be talking about the URL prefix field. I've always had the URL prefix field set to webroot but the Testing server folder is set to the mapped network drive because that's all it will accept.

I've attached a screen-shot of where I'm at now, which is how I've always been prior to posting this thread. This is the only way it will work. Adding http:// or just using \\ in the Testing server folder field will not work.

I'm sorry, I thought you were asking for advice but I see now that you are telling me the only way it will work. My setup already works fine, so I guess we're done. The difference is that mine works instantaneously and you get to wait awhile.

BTW your access method is wrong.

I'm not trying to be a smart ass here, man. I'm showing you how I've got it setup and informing you that when I try it how you told me to it doesn't work. I'd love to get instantaneous access to this tool but when I follow your steps it doesn't work at all...I can't even connect to the test server to do anything.

You guys used to have much better support than this. I could submit a ticket and I would explain things like this and you would screen share with me to figure out the problem. It usually involves some sort of bug with versions of your extensions I have installed. Check my support ticket history and you can confirm that.

I'm sure there's some reasonable explanation to what's happening here but again, when I configure the testing server the way you say it simply doesn't work. Can you give me a screen shot of how yours is setup? If my access method is wrong then tell me how to do it correctly, please. I don't know why I came off badly here..??

I just get a little tired when people make a bunch of assumptions and point the finger at everyone else. Let's clear some things up:

• "You guys used to have much better support than this" - If you read the Hours & Policy at the top of the forum you will see that WA is closed. I'm just a volunteer.
  
• "DataAssist is very slow" - They have no control over how you setup your network.
  
• "This is the only way it will work" - This is a statement not a question. You are working with the assumption that are no other ways.
  
• "It usually involves some sort of bug with versions of your extensions." - Many of the problems in the forums come from a lack of understanding of basic concepts of dynamic development.
  
• "Check my support ticket history" - Not only do I have no way of doing this, I could care less.

Read through your responses and see if you find anything that would make someone want to give up their free time. I merely pointed out that the fewer steps you force the OS to go through, the faster it preforms. You pointed out that mapping was the only way to go. To each his own.

10 Tips for getting quick help from a support forum
http://www.ipvac.com/kb/entry/149/