Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 8 years ago.
Improve this question
What is the effort to migrate an Access 2003 Application to Access 2007? Are there any problems converting mdb to accdb? Which modifications must be done?
This would be entirely based on the application being migrated, and is impossible for anyone to answer. It's like asking "How much will it cost to modernize the kitchen in my house?". Without knowing a lot more (what needs to be done, what kind of new appliances you want, the selection of cabinets, countertops and flooring you'd like, the labor and material costs in your area, the condition of the existing structure), it's impossible to predict.
Just migrate it, and deal with issues that come up. Make sure to back up the original application completely; if everything gets ruined, just restore from the backup and start over (or leave it as an Access 2003 app).
While it's true that it's a bit of an open question, there are some guidelines that will help you decide on how difficult it will be. Take a look at this:
http://www.sagekey.com/support_forum.aspx?g=posts&t=393
Since none of my DB's that I have upgraded involve the major pitfalls described in that article, I have had very little issues. One I did just last night took me about 30 minutes.
Related
Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 4 years ago.
Improve this question
Last year I started to develop a small "program" (not sure how this is called) in Access to help the family shop with the stock list and product prices, etc.
A few months ago, a client of the company started to ask for my Access's program because he needed one for its stock and they haven't found one yet. I was a bit scared of giving them the program because they could copy and steal my work.
Finally, my family suggested me to encrypt it in order to not be able to open its code, but I don't know how to do it.
So my questions are:
Is there a way to block the access to my VBA code in each Form? Through MS Access config or with more code, for me, it's the same.
Is there a way to block the duplication of its Forms or the whole file?
How can I secure my code?
I'm using MS Access 2016.
Edit: I've already got 2 downvotes and close flags, if you could explain to me in comments which thing do you think it's wrong I could try to fix it.
Access 2016 allows you to save as .accde format which is in effect an executable file. It seems that is what you need
Heres's how
you can also hide most of the Access environment so users can't really tell its Access
like so
Saving as an executable file as SEarl1986 said may be your best bet. I am unsure what happens to their database if you need to update your code tho.
Another way is to open Visual Basic, go to Tools, and "yourfilenames" properties, then under the protection tab you can "lock the project for viewing" and add a password.
It isn't foolproof as their is a method to break the password by editing the file with a hex editing tool, but it's a good lock that will deter most people. It will protect your code from prying eyes.
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 5 years ago.
Improve this question
I am curios why some prefer MYSQL over SQLITE, i am interested on learning MYSQL
SQLite is an embedded library, it requires no server process, and everything it saves is contained within a single, portable file. MySQL is an RDBMS server that's a lot more work to set up, but is multi-user, more scalable, and far more featured.
For example, SQLite is used for mobile applications as well as "development" instances of code where it's only lightly loaded. It can be used at scale but generally isn't, its simple design has limitations.
If you're writing a mobile application and need a local database, SQLite is not a bad call. Spinning up a huge, cumbersome MySQL process to do the same thing on a mobile device is a bad plan.
Although they're both "SQL databases" and have a lot of functional overlap, they're engineered to solve some very different problems. In some trivial use cases it might be an arbitrary choice as to which is best, but in most cases it's pretty obvious which of the two you need.
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 5 years ago.
Improve this question
I've been developing a small database for my summer internship and I need to write a manual/documentation for it aimed at both users and developers for future use. Thing is...I have no idea where to start or what information to include. Many people I work with have no idea what databases can do so I need to keep it as simple as possible. The database is implemented in Access and I experimented with the database documenter but I think that is overkill. Is there some kind of documentation standard that I can follow or anything of that nature?
As a starter for ten, I'd have thought that the user documentation should be task orientated.
(i.e: How to achieve 'X'.)
In terms of the developer documentation, defining the meaning of any non-obvious fields in your schemas, how they're used and the relationships between different tables, etc. would be a good start. (I'm presuming your VBA code is well commented, etc.) You may also want to examine the existing "Documenting Visual Basic with Doxygen" question/answer.
Just straightforward english if you are explaining a process.
If you have a series of Macros do a document highlighting to code used in each macro and the order it should be employed. This could aid someone down the line if they are trying to automate the process.
Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 7 years ago.
Improve this question
Here's my situation:
My client has an very large database. Currently, they fill out Inspection Forms by hand and manually put them into the database after the inspection. The forms are mostly checkboxes with very few areas for text input. They want to migrate from paper to tablets which are not specific to a single OS. When on the job site, the tablets will usually not be connected to the Internet.
I've been racking my brain for a few days trying to think of a solution. In what way could we record the offline data entry? Is there a way to synchronize the data when reaching an Internet source or would we be better off saving the current information and entering it into the db by hand when the inspectors are back at the office?
I was thinking to use HTML5/JS/PHP as it can easily be used on an android based, iPad, or Windows tablet and be cross compatible. I may be ruling out PHP as neither device should be able to run it locally.
Let me know if more information is needed.
Thanks in advance.
This might help you mate.
Getting Started with HTML5 Local Databases
Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 7 years ago.
Improve this question
I have an application deployed in Air, written in AS3 that the client wants to install and test, I have developed a simple license app, but he is pushing for a full license which he said he will fully pay on next Monday.
How would you create a procedure in AS3 to deactivate application next Monday? How secure will it be? Will simply changing machine date bypass this?
Changing the machine date will easily bypass your security mechanism. You need something more robust, which cannot be controlled by anybody other than you.
If your application is going to run connected to the web, you might be able to poll a remote server to see if the application is allowed to run or not. This is more flexible in that you can control the validity of the application without embedding dates into it.
There might even be off-the-shelf commercial components that do this for you.
But a more serious problem is that you have reason to distrust your client. Maybe you can collect part of the money when you deliver a limited-period beta and take it on good faith that he'll give you the remainder later.