J
JString
Greetings all.
I'm currently building an Access DB app for a small office of around 20
employees and the manager in charge has come up with an idea to have a task
list that is generated from records in Access and distributed to all
employees. Additionally, he needs to be able to create a back log of
employee appointments and time off, etc.
If we decide to go ahead with this project, I believe that creating the
needed links between Access and Outlook would be the most useful and the most
cost effective way to go about this. However, our IT support specialist
disagrees about this method as he says it would decrease portability in the
Access application. In other words, at some point down the road, the feature
I code for the client today will be guaranteed to fail and to create problems
for the client. But after speaking with the manager in charge, the client
believes that the benefit of this feature outweighs the cost of hiring a new
programmer in the future to make the necessary fixes.
So basically I'm stuck between a rock and a hard place. Our IT guy is
adamantly against it, but I feel that we should give the client what he wants
so long as he knows what he's in for.
To anyone with experience in this sort of issue, I need your opinions. Any
comments, suggestions or advice would be greatly appreciated. Thanks in
advance.
I'm currently building an Access DB app for a small office of around 20
employees and the manager in charge has come up with an idea to have a task
list that is generated from records in Access and distributed to all
employees. Additionally, he needs to be able to create a back log of
employee appointments and time off, etc.
If we decide to go ahead with this project, I believe that creating the
needed links between Access and Outlook would be the most useful and the most
cost effective way to go about this. However, our IT support specialist
disagrees about this method as he says it would decrease portability in the
Access application. In other words, at some point down the road, the feature
I code for the client today will be guaranteed to fail and to create problems
for the client. But after speaking with the manager in charge, the client
believes that the benefit of this feature outweighs the cost of hiring a new
programmer in the future to make the necessary fixes.
So basically I'm stuck between a rock and a hard place. Our IT guy is
adamantly against it, but I feel that we should give the client what he wants
so long as he knows what he's in for.
To anyone with experience in this sort of issue, I need your opinions. Any
comments, suggestions or advice would be greatly appreciated. Thanks in
advance.