Access 2007...

Hi Dave, been a while :)

I haven't installed Access on this one. I was curious about compatibility but it seems like compatibility isn't an issue. I'll see if I can get it installed, it's a legit copy albeit a bit old
You mean you are getting errors on your old PC then? Has anything changed?
 
Getting a "runtime error" is sort of a no-symptom symptom. Usually there is a specific number or text associated with the Runtime Error. Knowing the error number and/or text (in full) might give us a hint.
 
You mean you are getting errors on your old PC then? Has anything changed?
It's errors on the new one which led me to think there might be compatibility issues.

The old PC refused to boot in the end. I have a few databases that ran quite happily on the old machine but not so much on the new one.

I've ordered sn external drive, see if I can get this copy of Access loaded and take it from there. That seems to be the starting point.
 
It's errors on the new one which led me to think there might be compatibility issues.

The old PC refused to boot in the end. I have a few databases that ran quite happily on the old machine but not so much on the new one.

I've ordered sn external drive, see if I can get this copy of Access loaded and take it from there. That seems to be the starting point.
Don't you have a friend that would just copy the CD to a USB stick for you?
 
Don't you have a friend that would just copy the CD to a USB stick for you?
Hadn't thought that might work, I assumed it would need the original discs. I'm not brilliant with this stuff :)
 
It's errors on the new one which led me to think there might be compatibility issues.

The old PC refused to boot in the end. I have a few databases that ran quite happily on the old machine but not so much on the new one.

I've ordered sn external drive, see if I can get this copy of Access loaded and take it from there. That seems to be the starting point.
But didn't you say you don't have Access installed on the new PC. (#14) How can you be running an access database?
 
But didn't you say you don't have Access installed on the new PC. (#14) How can you be running an access database?
Runtime on the new one, that sort of installed itself when I transferred my invoicing package across
 
Runtime on the new one, that sort of installed itself when I transferred my invoicing package across
Well runtime will crash instantly on any unhandled error.

If you were getting errors on your old machine that you could recover from, you will not get that opportunity to resolve the problem with run time.

You are OK running well tested apps on run time, but you still really need a development machine available.
 
Agree with the last post. Runtime apps will crash the app and sometimes give very vague error messages. Your only reasonable way forward is to debug the error using the full version of Access, it's that simple.
 
Agree with the last post. Runtime apps will crash the app and sometimes give very vague error messages. Your only reasonable way forward is to debug the error using the full version of Access, it's that simple.
Installed access today and the database is running quite happily now so that's the first part of my question very much sorted. I'll have a look at the database over the weekend but am very hopeful that it can be modified to work as I want it to.

Excellent progress.
 
My idea is that the customer scans a key tag which carries a barcode each time they make a purchase. The database was just designed to collect entry data, as in when the customer entered the bar. I think it should be simple enough to add another field to that table to collect a value amount, like 30p or 10%, and then we should be able to query/report that amount as it cumulates and redeem it periodically as and when the customer wants to spend it.

I'll copy everything first so my ham fistedness can't do any harm and start having a look.
 
I'll copy everything first so my ham fistedness can't do any harm and start having a look.

EXCELLENT decision. Whenever you are about to do anything major, ALWAYS ALWAYS ALWAYS have a backup copy. When I was working for the U.S. Navy as a contractor, we ran daily backups, even weekends, since the systems were automated and transferred bulk data during slack hours - like weekends. Backups are the key to retaining your sanity. And restoring a database is maybe a hundred or maybe a thousand times faster than rebuilding a database by replaying transactions.
 
My idea is that the customer scans a key tag which carries a barcode each time they make a purchase. The database was just designed to collect entry data, as in when the customer entered the bar. I think it should be simple enough to add another field to that table to collect a value amount, like 30p or 10%, and then we should be able to query/report that amount as it cumulates and redeem it periodically as and when the customer wants to spend it.

I'll copy everything first so my ham fistedness can't do any harm and start having a look.
So what happens when I buy a pint?
 
So what happens when I buy a pint?

Ah, well the idea is that we have some printed keytags and each time you buy a pint you scan the keytag. My thoughts are that I can add a field to this current Entry database that will carry a cash amount - say 30p - and that the 30p increments will cumulate and we can redeem them at the bar. So if you have 30p x 10 if you spend £10 we can redeem the £3 (10 x 30p) and you pay the balance in the normal way.

We would have to manually redeem the £3 but that should take moments and the 'account' would always be accurate and up to date.

My limited knowledge of Access is really at an end with the FE/BE setup. The database was written by someone else - for me - and I don't know why he chose to do it this way. It works though, and it served us very well for it's original purpose.

To my mind it should be a case of an extra field or two in the tables and an extra form/query to deal with the inputting and redeeming. Any thoughts? I do have a habit of over simplifying things in my head :)
 

Attachments

Users who are viewing this thread

Back
Top Bottom