Custom template for a field - need help

Hi,

and thanks for your desire to help.

Here is what I did already :

1.) Created a View for a list of custom content type nodes - or to make it more obvious - I have a custom content type lets call it Product (for simplicity)
The View is used to show a list of all products (of content type Product) in a short version (like catalogue). On my View I only show a title, linked to node, an image, 3 more simple text fields and the most important 2 - Price field and Promo Price field (where the problem is)

2.) What I want to do - simply to have a custom template for the Price field - and to check (php) IF the Promo Price field for this Product is empy/does not exist
IF the Promo Price field is empty - then simply output the Price field normally
IF the Promo Price field IS NOT empty - then print a simple <span> so the Price field to display as striked-out

3.) I created a template for the Price field, named views-view-field--field-price-value.tpl.php and the Views module recognizes it and uses it when I rescan the template files.

4.) I can't get it working

The only code, that is somehow working is this one :

<?php if ($fields['promoprice_1']->content !== ""): ?>
<?php print '<span style="text-decoration: line-through">'?>
<?php print $output; ?>
<?php print '</span>' ?>
<?php endif; ?>

<?php if ($fields['promoprice_1']->content == ""): ?>
<?php print $output; ?>
<?php endif; ?>

But it doesn't work correctly, because it acts as if I'm asking are ALL of the Promo Price fields empty? And if there is even one, which is not empty - it strikes-out all Price field texts on all rows for all Products.

I've tried uncountable variations of

<?php if (empty($fields['promoprice_1'])) {

  print $output;
}
 else {

  print t('<span style="text-decoration: line-through">');
  print $fields['promoprice_1'];
  print t('</span>');
} ?>

and so on and so on...

Nothing seems to work, because it looks that I'm not calling the fields the right way I should.

That's why I need help, I hope somebody more familiar with the Views and it's way to address fields will be able to help.

By the way I'm using Table based output, I'm not sure if this is relevant to the solution.