Just keep management posted on progress and when they see deadlines slipping,
they'll ask why. You can explain then. Hopefully without prejudice and
finger pointing.
You say you have a developer who is experienced? In what? Take advantage
of their experience to lay out design requirements and perhaps work side by
side with the developer to get some of your Excel VBA knowledge imparted to
them. There's little doubt that the developer will know WHAT needs to be
done and how to attack the problem, it is the HOW that is slowing him/her
down, and that's where working with them can help you both. And you can help
turn what seems to be a liability into an assett.

"xl" wrote:

I've found that many companies do not have the level of expertise
commensurate with the level required to weed out the hard core Excel
developer from the Access/VB/.NET developer that 'dabbles' in Excel VBA.
After all, VBA is all the same and it is only Excel, or so they think. With
that said, I am in a position in where I am working under tight deadlines
and have a developer that is experienced, but struggling with Excel VBA.
Essentially, I am carrying all the weight of two individuals. I believe
management is on to the fact that something is not right, but how do I
tactfully explain my ordeal? The tech interview they gave to me was a joke
so I can see how easily someone can slip through the cracks by winging it.