12M Measure Periodic/YTD application

Dear all,
When looking into the PeopleMgt application, we noticed that the 12M measure is calculated differently in a periodic application for AST/LEQ accounts.In periodic application, it will take the avg of 12 months whereas in a YTD application, it will take the sum of last 13 periods/13. In the periodic application, it means that months without data are not being considered which leads to an incorrect 12M Measure.
Looking into AppShell I don't see 12M Measure as a custom measure. Being not involved in the measure setup previously, I would like to know your opinion. Acc to use the 13periods/13 seems more logic. Once we take a decision, can I just change the formula in the MeasureFormula/MeasureFormulaYTD table? Or some other settings I need to consider?
Thanks in advance!
Kind regards,
Sofie Luyten

Hi Sofie,
Formula from 12M measure is an MDX formula.
If that is correct then you just have to place that formula into table MeasureFormula.
Please make sure you have the correct value for Solve Order. Probably in your case must be bigger than 3 because actually you need the evaluation of your formula to be done after the evaluation of other measures.
After you insert the correct formula into table MeasureFormula you have to process application using Modify Application and make sure you check both flags: "Reindex and Process application".
You have all the information about customer measures into HTG from http://wiki.sdn.sap.com/wiki/display/BPX/EnterprisePerformanceManagement%28EPM%29How-to+Guides
"How to Manage BPC &M Time Dimensions and Custom Measures "
Regards
Sorin Radulescu

Similar Messages

BPC 7.5 Periodic and QTD issue on YTD Application

All,
Our BPC 7.5 SP 6 YTD BPC application has an issue when running EVDRE reports using Periodic or QTD measures. YTD EVDRE reports produce correct results. The Periodic and QTD measures work just fine as long as there is data in every period but as soon as no data is found in a subsequent period the system can not do the calculation. It does not know how to take 'nothing' and then subtract a prior period value. It somehow needs to treat the non existance of a record as 0 but it does not do that. For example if the YTD May balance was 100 and YTD June was 500, if you request the periodic value for June it will take 500 - 100 and give you a 400 result which is correct. In my second example, let's say YTD May balance was 100 but the balance went to 0 in June. BPC does not load 0 amount so there is no record in June. If you run a report requesting the June periodic value you will get no result as it can not handle the situation where there is no record in June.
A while ago I worked with SAP on this and was advised to install OSS note 1405993 which FIXED that problem. Great news until at a later date our periodic reports stopped finishing and would give the message 'EVDRE encountered an error reading data from the web server'. It would retry in 30 seconds and error over and over never finishing. I again reported this to SAP who gave me more efficient Periodic and QTD formulas via note 1505778. I installed the more efficient formulas and the EVDREs now finished but it brought back the original problem where Periodic/QTD reports would produce incorrect results if there was not data in all periods. I again reported this to SAP without success. I have been advised to do the calculation myself in the front end (e.g.EXCEL) which just seems unaccepable.
I have found another thread http://scn.sap.com/thread/3203570 <http://scn.sap.com/thread/3203570 where this same problem occurs in BPC 10.0 - very sad to hear that! In that thread people have talked about using 'custom' formulas and say they work. The formulas I have in place are the ones found in note 1505778 to calculate periodic and QTD. Yes, I created the formulas for the Periodic and QTD measures but I did it based on direction from SAP. Is that what everyone refers to as a 'custom' measure? Does anyone have other formulas where they somehow tell the system how to handle the issue if there is no data found in a subsequent period when trying to run periodic or QTD reports on a YTD system? If so I would be most grateful if you could share them or any other details you have on the subject. Thank you.
Thank you,
Vicki Shrontz

Easy, just remember that my TIME dimension name is PERIODS and my ACCOUNT dimension name is INACCT:
For YTD cube (in my sample) we have 3 measures:
YTD:
MEMBER [MEASURES].[YTD] AS 'IIF(([%INACCT%].CURRENTMEMBER.PROPERTIES("2/CPMB/ACCTYPE")="INC" OR [%INACCT%].CURRENTMEMBER.PROPERTIES("2/CPMB/ACCTYPE")="LEQ"),-([MEASURES].[/CPMB/SDATA], CLOSINGPERIOD([%PERIODS%].[LEVEL02])), ([MEASURES].[/CPMB/SDATA], CLOSINGPERIOD([%PERIODS%].[LEVEL02])))' SOLVE_ORDER=3
PERIODIC:
MEMBER [MEASURES].[YTD] AS 'IIF(([%INACCT%].CURRENTMEMBER.PROPERTIES("2/CPMB/ACCTYPE")="INC" OR [%INACCT%].CURRENTMEMBER.PROPERTIES("2/CPMB/ACCTYPE")="LEQ"),-([MEASURES].[/CPMB/SDATA], CLOSINGPERIOD([%PERIODS%].[LEVEL02])), ([MEASURES].[/CPMB/SDATA], CLOSINGPERIOD([%PERIODS%].[LEVEL02])))' SOLVE_ORDER=3
MEMBER [MEASURES].[PERIODIC] AS 'IIF(([%INACCT%].CURRENTMEMBER.PROPERTIES("2/CPMB/ACCTYPE")="INC" OR [%INACCT%].CURRENTMEMBER.PROPERTIES("2/CPMB/ACCTYPE")="EXP") AND NOT ([%PERIODS%].CURRENTMEMBER.PROPERTIES("2/CPMB/PERIOD")="TOTAL" OR [%PERIODS%].CURRENTMEMBER.PROPERTIES("2/CPMB/PERIOD")="Q1" OR [%PERIODS%].CURRENTMEMBER.PROPERTIES("2/CPMB/PERIOD")="JAN" ), [MEASURES].[YTD]-([MEASURES].[YTD],[%PERIODS%].LAG(1)), [MEASURES].[YTD])' SOLVE_ORDER=3
QTD:
MEMBER [MEASURES].[YTD] AS 'IIF(([%INACCT%].CURRENTMEMBER.PROPERTIES("2/CPMB/ACCTYPE")="INC" OR [%INACCT%].CURRENTMEMBER.PROPERTIES("2/CPMB/ACCTYPE")="LEQ"),-([MEASURES].[/CPMB/SDATA], CLOSINGPERIOD([%PERIODS%].[LEVEL02])), ([MEASURES].[/CPMB/SDATA], CLOSINGPERIOD([%PERIODS%].[LEVEL02])))' SOLVE_ORDER=3
MEMBER [MEASURES].[PERIODIC] AS 'IIF(([%INACCT%].CURRENTMEMBER.PROPERTIES("2/CPMB/ACCTYPE")="INC" OR [%INACCT%].CURRENTMEMBER.PROPERTIES("2/CPMB/ACCTYPE")="EXP") AND NOT ([%PERIODS%].CURRENTMEMBER.PROPERTIES("2/CPMB/PERIOD")="TOTAL" OR [%PERIODS%].CURRENTMEMBER.PROPERTIES("2/CPMB/PERIOD")="Q1" OR [%PERIODS%].CURRENTMEMBER.PROPERTIES("2/CPMB/PERIOD")="JAN" ), [MEASURES].[YTD]-([MEASURES].[YTD],[%PERIODS%].LAG(1)), [MEASURES].[YTD])' SOLVE_ORDER=3
MEMBER [MEASURES].[QTD] AS 'IIF(([%INACCT%].CURRENTMEMBER.PROPERTIES("2/CPMB/ACCTYPE")="INC" OR [%INACCT%].CURRENTMEMBER.PROPERTIES("2/CPMB/ACCTYPE")="EXP"),IIF([%PERIODS%].CURRENTMEMBER.PROPERTIES("2/CPMB/TILEVEL")="QUARTER",[MEASURES].[PERIODIC],IIF([%PERIODS%].CURRENTMEMBER.PROPERTIES("2/CPMB/TILEVEL")="MONTH" OR [%PERIODS%].CURRENTMEMBER.PROPERTIES("2/CPMB/TILEVEL")="WEEK" OR [%PERIODS%].CURRENTMEMBER.PROPERTIES("2/CPMB/TILEVEL")="DAY",SUM(PERIODSTODATE([%PERIODS%].CURRENTMEMBER.PARENT.LEVEL, [%PERIODS%].CURRENTMEMBER),[MEASURES].[PERIODIC]),NULL)),[MEASURES].[YTD])' SOLVE_ORDER = 3
B.R. Vadim

Periodic values for INC/EXP accounts in YTD application (first period only)

Greetings,
I have a YTD application. INC/EXP account balances are imported as YTD.
When I choose the Periodic measure for the FIRST period of the year, BPC calculates the difference between the YTD value for the first period (which is really the priodic value for that periodic) and the YTD value for the last period of the prior year.
The result is incorrect. For the firt period I only want BPC to use the first period's value.
Greatly appreciate your guidance.
Regards,
Craig

Hi,
you have to update the MDX formula in the MeasureFormula table for the row such as NAME='Periodic' and isYTDapp='1' with the following formula:
IIF(([%ACCOUNTDIM%].PROPERTIES("ACCTYPE")="LEQ" OR [%ACCOUNTDIM%].PROPERTIES("ACCTYPE")="AST") OR ([%TIMEDIM%].PROPERTIES("ISBEGINNING")="1"),[MEASURES].[YTD],[MEASURES].[YTD]-([MEASURES].[YTD],[%TIMEDIM%].LAG(1)))
Then you have to check that you have ISBEGINNING=1 for each january member.
regards,
Romuald

(Strange) Currency Conversion on YTD Application

Hi experts
I found a wrong currency conversion on YTD Application and my customer also has the same problem.
Here is the example:
Rate Application
2008.JAN 1 EUR = 1.2 USD
2008.FEB 1 EUR = 1.2 USD
2008.MAR 1 EUR = 1.4 USD
Finance Application (a YTD application)
CV Time: YTD
2008.JAN 10 EUR
2008.FEB 20 EUR
2008.MAR 30 EUR
CV Time: Periodic
2008.JAN 10 EUR
2008.FEB 10 EUR
2008.MAR 10 EUR
For the correct currency conversion (to USD), I should get
2008.JAN 12 USD (10x1.2)
2008.FEB 12 USD (10x1.2)
2008.MAR 14 USD (10x1.4)
2008.Q1 38 USD
But the result is
2008.JAN 12 USD (10x1.2)
2008.FEB 12 USD (10x1.2)
2008.MAR <wrong> USD (10x???)
Is it a bug or my wrong configuration ?
ps. you can try it
Regards,
Halomoan
Edited by: Halomoan Zhou on Jun 20, 2008 8:54 AM

What you see is normal behaviour:
when you do a ytd currency conversion, the YTD LC amount will be translated against the entered rates.
If you then look to periodic data, the ytd previous period amount will be deducted from the ytd current perid amount by OLAP.
This then means that you cannot calculate the periodic LC amounts against the entered rates.
If this wasn't the case, the calculation below will not work on converted numbers:
YTD februari + periodic march = YTD march
I think that the calculation above must always work. BUT I know of one customer that didn't wanted this behaviour, they wanted that the periodic values AND the ytd values calculated against the same entered rate. There are several ways to achieve this; we added a member in the subtables dimensions to store the difference and then adjusted the measures calculation so that this difference was picked up by OLAP when selecting the periodic measure.
AGAIN: I didn't like this because the calculation of "YTD februari + periodic march = YTD march" is in my opinion a holy one.... But the customer is always right
Hope this helps,
Alwin

P & L report for current period,YTD and previous YTD

I am trying to create a P & L report with the columns for current period,YTD and previous YTD, I have include the measures as the key of columns, which by using period or YTD we can retrieve the current period and YTD column, is there as easy way to get the previous YTD? although I can get it by using evtim to het every month and calculate the previous YTD.

resolved, just need to bring both time and measures in the columns

Can I measure period with USB 6501?

Hi,
I was told that I can use the one counter in the NI USB 6501 to measure period. So, I wrote this little VI, modeled after the VI I have that measures encoder period using the counters built into the NI cDAQ 9174 with the NI 9401 digital I/O module. I have my encoder wires GND and 5VDC on terminals 1 and 2, respectively. Also, I have encoder channel A and Channel B wires connected to terminals 9 (P2.7) and 24 (P0.7) respectively. With the MAX, I can count edges with this wiring. The purpose of this VI is to display an average value of 25 period measurements of the encoder. The encoder (120 cpt) is turning at about 2-5 rev/second, so, not that fast, maybe a total of 500 period per second; should be easy for this counter. I'm just spinning it with my finger, so, not that fast.
Please advise how to use the USB 6501. I can't find any wiring instructions, other than the pinout, but, the pinout doesn't tell you which channel is the counter gate on the USB 6501, so, I found a response on MAX at channel 24.
When I run this, the array is correctly initialized to 0.5, but, then I get this error, 200431. I found some things on the forum that suggest I cannot measure period, that I can only count edges. Should I throw this 6501 away?
Thanks,
Dave
Attachments:
USB 6501 error.docx ‏24 KB
USB 6501 period measurement.vi ‏26 KB

The 9178 also only has 4 counters.
Do the 5 period measurements actually have to take place at the same time? Sometimes it might make sense to cycle through the channels to reduce the number of counters used (you wouldn't have to rewire connections or anything as the input terminals are software-defined). Switching from channel to channel in software should take on the order of ms depending on which hardware you end up using.
The 9171+(9401/9402) is a relatively cheap way to add additional counters to a system as the 9171 chassis has 4 counters just like the 9174 and 9178.
Best Regards,
John Passiak

Measure Period with error out.vi

I am using LV6.0. Can Measure Period With Error Out be found in the functions panel? If not where it is? If not there can it be imported into LV6.0?

labview1958,
Are you looking for a specific VI called Measure Period with Error Out.vi or are you asking about any general function that can be used to measure the period of a signal and includes error handling? If you are looking for a specific VI, I'm unaware of it, so I won't be much help there. If you're looking for any function to do it, have you looked at the VIs called Measure Pulse Width or Period.vi or Pulse Width or Period Meas Config.vi? They are located in the Data Acquisition>>Counter palette. The Measure Pulse Width or Period.vi does not include error handling, but it would be extremely easy to add it. The Pulse Width or Period Meas Config.vi DOES contain error handling, but it only configures the counter to measure the period, it doesn't actually measure it. These, of course, are for TTL signals coming into your hardware device. If you are reading waveform data from a file and want to calculate the period of that signal, these won't do much for you. So what exactly are you wanting to take a period measurement on, a physical signal, physical signal data points from a file, or some other method?
Tyler S

Measuring period of a pulse

Hi
I m measuring period of a pulse coming from a magnetic proximity sensor. There r two porblems.
1. I want to monitor the data coninuosly in a while loop but the moment it waits for pulse it doesn't stop and hangs for some time....
2. While monitoring the data , sometimes high values appear ....... but these values are unwanted. Once if i want to filter out thse values and see only the exact pattern , how to make it...
PLz. do answer these queries at earliest......
Thanks and regards
GNS

Hi,
To monitor data continuously without hanging:
1. Configure your counter to do "buffered period measurement"
2. In your loop, query the counter for "available points" using "Counter Get Attribute.vi"
3. When == 0, do nothing. When > 0, read that # of points from the counter buffer. This way, you're never asking for any data that isn't already there and your loop won't ever have to hang and wait for it.
4. Accumulate/store/graph your data according to the needs of your app.
To filter out unwanted high values:
First, I'm assuming that your "high values" are high frequencies, thus small periods. If so, these may be caused by sensor and/or electrical noise. The best thing to do first is try to reduce/eliminate the noise at its source. Failing that, there *may* be a way to make good estimates of the correct data, but it could get pretty tricky. Here's an outline of a way to think about and deal with the simplest case -- where you know the expected measured frequency and it's very nearly constant over time.
The characteristic of such a noise glitch would be a a pair of transitions in rapid succession, either low-->high followed by high-->low or vice versa. Either way, you'll pick up one of those transitions in your buffered period measurement. The trouble is that it may happen anywhere within the nominal period, possibly more than once.
Let's first look at a case where the nominal period is 1 msec +/- 20% and there is one glitch of duration 0.1 microsecond, occurring at the 70% point of the real period. The measurement should show one period of duration 1.0 msec, but the noise glitch will cause you to receive instead two periods of duration 0.7, and 0.3 msec.
The simplest correction would be to simply trash all measurements outside the acceptable range of [0.8, 1.2] msec, including these two. Note however that a noise glitch occurring at the 90% point would lead you to trash the 0.1 msec measurement, but believe and keep the 0.9 msec measurement. Note also that if noise glitches are distributed randomly in time, you would end up keeping 40% of such erroneous data (glitches in either the first 20% or final 20% of the real period).
Another correction would be to estimate the period interrupted by the glitch. Start by assuming no more than one glitch per legitimate period. Since the glitch subdivides the true period into a pair, you can re-create the true interval by summing the pair of periods. The catch is to identify which pair needs summing.
The smaller of the pair will show a period <= 50% of the real period, and can be identified. However, the larger of the pair cannot always be identified. The larger of the pair can be anywhere from 50%-99.999% of the real period and may located either right before or right after the smaller of the pair. If you wish to recreate the real period, you'll need to make a mathematically educated guess about which adjacent period to consider as the "larger of the pair."
This is tricky enough as a post-processing exercise, but it's even worse when you process the data as it comes in. Then there will be times where the last element in the buffer is the "smaller of the pair" and you don't yet have the "larger of the pair" data. There will also be (rarer) times when the last element is the "larger of the pair" but you can't yet know that it needs to be summed with the next "smaller of the pair" measurement.
Now consider a case where there could be two or more glitches inside true period. You'll need to evaluate the best choice of summing any two, three, four, etc. consecutive periods to reconstruct the real period. {note that for n glitches and a +/-20% acceptance criteria, then (2/5)^n of the glitched intervals will produce one measurement within the +/-20% bounds.} In such a scenario, I would advise working *really hard* on eliminating the glitches at the source.
Whew, that's a mouthful and a half! Reply if you'd like an outline for an alternate approach, involving buffered semi-period measurement...

Counter roll-over when measuring period

Hi,
I'm using PCI-6251 counter 0 to continuously measure the period of a signal, and I notice there are occasionally error readings. Since the counter can roll over when it reaches 2^32-1, I need to know what will happen to the period measurement when counter roll overs. Would anyone please help me?
Thanks.
David

The count value will simply wrap-around back to 0 and then continue to increment. I can think of a few ways to handle this:
1. Specify a slower timebase for the measurement. If you go from, say, 80 MHz to 100 kHz, it'll take 800 times as long a period to cause rollover. This method is pretty simple to implement, but not all apps can accept the loss in precision.
2. You can use a 2nd counter to be sensitive to the 1st counter's "terminal count". This gets a bit complex, so you may need to do more research on some of the terms that follow.
An internal pulse signal is generated on the board when the 1st counter rolls over from 2^32-1 back to 0. It's commonly known as "terminal count" or TC. You'll need to configure a 2nd counter that also measures periods of your external signal, but which uses those TC pulses as its timebase signal. You may need to fiddle with the "Duplicate Count Prevention" property on the 2nd counter so that it will buffer values of 0 during the majority of intervals where no TC pulse occurs. During the intervals where rollover happens, the 2nd counter will count how many times it happens.
You would further need the 2 counters to be started off a common "arm start" trigger to keep their data sync'ed.
3. Software method. You can query the DAQmx Channel property "Counter Input -> General Properties -> More -> Terminal Count Reached". When you get a 'True' output, the property resets such that subsequent calls will return 'False' until the next rollover occurs. The problem here is trying to correlate this software-detected rollover with a specific period in the 1st counter's measurement buffer. You'd probably also need to be querying and tracking the DAQmx Read property for Total Samples Acquired both before and after the TC event. Even then you might not always be able to determine unambiguously which interval had the TC event.
-Kevin P.

Consolidate YTD in Actual and its relation Org by period in Application set

Hi Peers,
Make me clear for the following
Actual data: the data which is past for 12 month periods of data apply the same with Scenario dimension member"Consolidate YTD. and next Org by period is Future related now please explain me these concepts how,why,where

Hi,
Please go through the below link for your answer.
HFM Scenario
Regards
Dev

Measuring period in time critical loop

I have a loop running at 6 ms for all my application code. I need to integrate a measurement for period of a TTL signal into this loop ( connected to my gate input of a 6602) but all the example VI's I have looked at wait for the counter to respond before moving on - This is a problem with the low speed I am looking at, and when the speed is zero ( hence the overcount kicks in). What is the best way for me to measure a period given that I am restrained by my overall loop time. I have set up a VI which looks at the counter every tenth cycle, but I would rather have the data more frequently than this using some sort of 'peek' type buffered approach.

If I understand correctly, you have a loop that must run continuously irrespective of whether there is a period measurement available. And if there is a period measurement available, you want to use that value in your loop.
If all that's correct, just put a case selector around Counter Read Buffer in your loop. Only call Counter Read Buffer when there is a period measurement available.
How will you know when there is a period measurement available? Call Counter Get Attribute, checking "available points" attribute ID.
Now, your loop must call Counter Get Attribute every time, but that is a small price to pay compared to locking up the loop waiting inside Counter Read Buffer. Let me know if this helps.

Using a rotary angular encoder to measure period of pendulum

Hi,
I'm new to Labview (I hope I've posted this in the correct section) and am trying to measure the period of a physical pendulum. I'm using an Omron rotary angular encoder (E6D-CWZ 2 C) and the SCB-68 NI card. Basically I'm trying to interface my pendulum to the PC in order to analyse the motion.
I'd appreciate if anyone has any advice or can point me to a tutorial that might help.
Thanks,
Sarah

Hi Sarah,
Interesting application--I think your best best is to use the counters on the 6024E as follows:
1. Configure a Count Edges Task (the E Series cards don't directly support quadrature encoder tasks).
2. Use the A output as the edge to count, and the B output as the direction control line.
3. Set an initial value such that the bottom of the arc is your "0 reference" (e.g. if you are starting the pendulum 1000 encoder ticks above the bottom of the arc then your initial count should be -1000).
4. Every time the counter rolls over it will produce a pulse on its internal output. This will be every time the pendulum reaches the bottom of the arc.
5. You can perform a period measurement using the 2nd counter on the 6024E. The line that you want to measure will be the other counter's internal output.
This isn't the most straightforward configuration so you should probably start out by combining shipping examples. I would start with the following two examples (which can be searched for in the Example Finder by navigating in LabVIEW to Help >> Find Examples...)
Count Digital Events.vi
Meas Pulse Width-Buffered-Cont.vi
I would start out by getting the Count Digital Events example to work so that the value is 0 every time the pendulum reaches the bottom of the arc, then you can try adding in the Meas Pulse Width example to perform the period measurement.
Best Regards,
John Passiak

Measure period and pulse duration of ttl level continuously

Hello,
i want measure the period and pulse duration continuously of two signals with an usb-6009. Every 8s there is a high pulse for 15ms. I want to measure length of the pulse and pause. Can someone help me? I can`t get a start up with this problem.
The four measurements (two channels two measurements per channel) are a dataset. This dataset should be stored in a textfile continuously. But this not a problem.
thankyou
Schwede

Hi Schwede,
Thanks for the update - Im now back in the office!
I have some bad news, your using the wrong device - you need a device with at least two counters - to acquire for two signals. But, secondly,(see specs), the counter measurements support by the USB 6009 doesn't include pulse or width measurements.
The specs for the USB 6009:
Counter
Number of counters ................................1
Resolution...............................................32 bits
Counter measurements ...........................Edge counting (falling-edge)
To acheive the functionality you require I would recommend a USB 621x:
Number of counter/timers ............... 2
Resolution ....................................... 32 bits
Counter measurements.................... Edge counting,
pulse,
semi-period,
period,
two-edge separation
Also, this link is rather useful also:
How Many Counters Does Each Type of Counter Input or Output Task Take?
http://forums.ni.com/t5/forums/replypage/board-id/170/message-id/363123
Please let me know if you have any other questions.
Kind Regards,
Kind Regards
James Hillman
Applications Engineer 2008 to 2009 National Instruments UK & Ireland
Loughborough University UK - 2006 to 2011
Remember Kudos those who help!

BPC Custom Measures for YTD AVG and QTD AVG

Hi,
I am am trying to modify MDX logic for YTD and QTD Measures to calculate the YTDAVG and QTDAVG. I am having no luck so far. Anyone, done that before or knows how to do it?
Thanks,
Mark

Hi Mark,
Did you get a chance to look in to the following How too
[how to create custom measures|https://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/206cb499-990f-2c10-5aa8-84d891894979]
-sanjay.

My application conflicts with another Measurement Studio based application.

Hi,
Our instrument is made by a third party, and they appear to use Measurement Studio in the development of their control software.
We use Measurement Studio when developing our test software. When we install our test application on a production machine (no programming environment installed), we sometimes get a message about only being able to use controls for 5 minutes in an "evaluation-only" mode.
It is clear that there are some library file revision conflicts, e.g.: in cwui.ocx and presumably others. The third party is using a slightly different revision of these files to ourselves. What is the the best way to consistently resolve these conflicts?
Thanks,
Richard Brockie

Hi Richard Brockie,
You are correct in assuming there is a conflict with cwui.ocx.
If the target computer does not have Measurement Studio, it will not contain the .ocx and .dll files required for the executable to run. Microsoft Visual Studio .NET has a Setup and Deployment Projects type that allows you to create a MSI installer that finds all of the dependencies for the project and then installs them on the target machine when the setup is executed.
I've included the following link that demonstrates the process of creating an installer for a Windows application, using .NET or Active X controls.
http://digital.ni.com/public.nsf/websearch/ED87C183E056CAC386256DF1004E54C6?OpenDocument
Please respond if you have further questions or if this does not resolve your issue,
Chad AE
NI

12M Measure Periodic/YTD application

Similar Messages

Maybe you are looking for