Problem using Excel Automation Task

[Sesshoumaru]

Hi, I need help, I've been writing some tasks with AA, and I want to set some data into an Excel spreadsheet. I use variables to access to the spreadsheet (file location, active sheet, session name). The problem comes up when I run the task, the spreadsheet is opened but the task stops when it reaches sentences like:

Go To Cell "$variableCell$". Session: $sessionName$
Activate Sheet By Name= $active_sheet$. Session: $sessionName$

When I write the task without use variables, it run perfectly, but what I need is to use those variables. I hope you can help me with this issue.

[forumsupport]

Hello,

Can you please upload your task so we can look into it and suggest the viable solution?

Using Excel commands you can automate the mentioned task very easily.

You can view demo on Excel commands usage from, http://www.tethyssolutions.com/AAExcelIntegration.html

For your convenience, we have created a sample task that uses variable for, file location, session name, active sheet and cell number. To run this task,

. Please copy it under location, 'C:\...\My Documents\Automation Anywhere\Automation Anywhere\My Tasks' folder.
. Copy Book1.xls under C:\.

Note: Automation Anywhere 5.5 is required to run this task.


Hope that helps.

[Sesshoumaru]

Hi there, first I want to thank you for your answer, I'm glad of know that "I'm not alone" jeje.

Yesterday I spent some time checking what was happening, and I found the problem and its solution. First I have to say that I forgot to mention something about the kind of variables I was using. These variables are read from an text file. Surely you can say that this fact does not make difference, and I agree with that.

The whole process that I'm trying to automate writes the values for these variables into the text file. So, analyzing the text file I found that the path for the spreadsheet was like this:

D:\SiteA\Task\Task\DocsToWrite\VCE_D009\PBX\\VCE_D 009_PBX_31-08-09 To 04-09-09.xls

As you can see, the process was writing the path with two '\' characters just before the name of the file. I fixed the task so that will not happen again. Finally, running the task after that fix, the original problem was solved.

I must tell I'm not sure how can an extra '\' character could stops the task; but for now, I'm glad the problem is solved.

Once again, thanks a lot for your attention, I hope my experience could help someone else in future.