EmployedAgain
Programmer
I am assuming the answer is no from what I have read (ie no new objects). I have a complicated database I created for a client who now wants it distributed to people that may not have Access installed. Theres a form that deals with testing and the test is created on the fly as each one is different and there are many different tests. There is code behind the dynamic form as well. And to top it all off its a split database with replication.
We already ran into issues with the dynamic form when replication was set up. I've tried locking down the VB code using the protect property but it comes up with a popup asking for the vb password when the dynamic form is created. (Protecting the code is the other concern)
My questions are: 1. Am I for sure not going to be able to package this database using the developer version (that I dont have yet).
and
2. IF I would redo the whole project in Visual Studio (which we also dont own) or something, would it solve the problem with the dynamic form in a packaged application?
OR
3. am I SOL
TIA
B
We already ran into issues with the dynamic form when replication was set up. I've tried locking down the VB code using the protect property but it comes up with a popup asking for the vb password when the dynamic form is created. (Protecting the code is the other concern)
My questions are: 1. Am I for sure not going to be able to package this database using the developer version (that I dont have yet).
and
2. IF I would redo the whole project in Visual Studio (which we also dont own) or something, would it solve the problem with the dynamic form in a packaged application?
OR
3. am I SOL
TIA
B