Yes, this is an ASP question, but it is also an access question.
I have finished a database, but it is more of an application. It is heavily reliant on visual basic and controls. I am happy with it,
The manager thinks it should be a web page (??)
I know ASP can interact with Access and be a front end, but Im struggling to find a point in using it.
So what Im after are reasons why NOT to use ASP. What are the limitations. I have read about people saying that access is the best front end for access, so please tell me why this is.
As a side note, and probably not relating to access, but no doubt something you may have encountered:-
What is the best way to do professional database applications?
Is it access?
Is it access with something else?
Is it something else?
Thank you
I have finished a database, but it is more of an application. It is heavily reliant on visual basic and controls. I am happy with it,
The manager thinks it should be a web page (??)
I know ASP can interact with Access and be a front end, but Im struggling to find a point in using it.
So what Im after are reasons why NOT to use ASP. What are the limitations. I have read about people saying that access is the best front end for access, so please tell me why this is.
As a side note, and probably not relating to access, but no doubt something you may have encountered:-
What is the best way to do professional database applications?
Is it access?
Is it access with something else?
Is it something else?
Thank you