I have a couple of basic questions that I can't seem to find an answer to.

1. I know that it is possible to save an Add In query to use later - my question is whether it is possible to save the spreadsheet so that it saves the query with it rather than have to open the spreadsheet and then find the correct query that goes along with it?

2. Is there a way to force it so that if the spreadsheet is opened it enforces LAUA security on the user that is opening the spreadsheet so that they don't see data that they should not - or do we have to save the spreadsheet in a secured location based upon the same security we have in Lawson?

We are on 2.0 of add ins - I don't know if this is something that is changed in a new release now...

Thanks!

I'm not an Add-Ins guru, so I'll pass on trying to answer your questions, but I recently referred a client to last year's CUE presentations on Add-Ins and they found them quite useful.

http://hpsale37.lawson.com/lu/addins/main.htm

g'luck

We use addins extensively and I'm not aware of a way to save the addin as an integral part of the spreadsheet template. I usually just use a common naming convention so that I can keep things straight. We're on version 2.0.4.

I'm not an expert on security so I can't answer that question. We usually only allow a select few power users access to addins though. Maybe that's why.

It was always my understanding that the addins do follow LAUA security, however, so few users have access here that I can't really confirm that - sorry!! To my knowledge, there isn't a way to save the query itself to a spreadsheet - however, if different users need the same query what we do is have the dme's on our shared drive (restricted access anyway), and anyone who has the add-ins can use the same query. That probably doesn't really address your question, though - :blink:

So far as I know, no, it is not possible. The Add Ins do not supply an Office-compatible ODBC driver, which would make this possible.

You can look for yourself at the VBA for the Lawson Add Ins macros and see that the only actions that they take automatically upon opening are to add themselves as menu options. You will need to use NTFS or share permissions to control access.

I don't have a direct answer for the LAUA issue. That is to say, I have never seen the LAUA issue directly addressed with MS Addins. However, I have some anecdotal evidence that MS Addins MUST follow your LAUA rules. When you do an upload in MS Addins (say to the IC11), the User ID attached to the records is the ID used to log into MS addins. Conceding that the Addins User ID and the Lawson ID do not HAVE to be the same, as long as they had the same LAUA parameters, you should be fine.

I also do not have a direct answer for the question of having Excel automatically open MS Addins. It seems to me that you could create a desktop shortcut that would have properties that would kick off Addins as a part of an Excel startup macro. I don't think I would want to have this be the default for Excel, but that would really depend on personal preferences.

If you are trying to distribute the Addins query as a viewable report, and not as a workable/editable spreadsheet, you could send the DME call as an URL link. It does not connect back to Excel when the results are presented. The really nice aspect of this choice is that you can send the link to people who do not have Excel or Addins installed and they can still benefit from the query. I can go into more detail if this seems like it might be a feasible option.

Just my $0.04 (inflation and what-have-you)
rw