ms access 2003

[softy]

Guy's and Gal's

I have a database that is based on MS access that I am having trouble
with. I actually paid someone to create this for me but they refuse help
as they have gone out of business! (wonder why-)

First, before I show that I am a complete idiot and describe the fault,
** am I in the right group for that type of help ** ??

Softy

 

[softy]

BTW... the database is for Pest Control

 

[oldblindpew]

Softy,
There is considerable expense and effort in developing a full-blown
custom-made application. What makes things affordable is spreading the cost
among many end users. Since you paid someone to develop your application,
you may be a small company with maybe just one location. I think your
choices are to either spend a very long time acquiring the knowledge it takes
to do Access yourself, or, find and pay another consultant to continue
developing your application.

There are some very knowledgable and helpful people on this forum, but there
are practical limits to what can be accomplished here. Vague questions
cannot be answered clearly in any case, and extremely broad and complex
questions tend to get bogged down in details. The best results come when a
knowledgeable developer asks a very specific and narrowly focussed question.

I would suggest you try picking out one thing you are having trouble with in
your application, learn as much as you can about it by "getting under the
hood" and figuring out specifcally which parts are not working, and then ask
your question accordingly.

Best of luck,
OldBlindPew

 

[softy]

Sorry for the "vague" original question but I am that way about this and
what its doing...and also, I was not sure if I were in the right NG

First, the DB belongs to the other 1/2 and I have never really used it.
Just looked at what she told me and tried a few things. My knowledge of
MS Access is very limited.

As best I can....
The database seemed to have run out of job numbers for 2009. All job
numbers start with the year prefix i.e 08xxx or 09xxx.
We gave up using it around August 09 as new jobs entered were gone next
day...and when logging in, a message popped up saying

QUOTE
"The job ID is not using the current year as count prefix, do you wish
to update it to the current year"

If we change the date of the computer to 2009.... and start the database
so the DB thinks its 2009... the same above error pops up. Closing and
changing back to 2010, the error is gone.

How here today, gone tomorrow was happening I have no idea

Now playing with it in 2010, it seems to be working again but obviously
not fixed

We did take it down to the local computer shop. He said he fixed it by
"adding more numbers"?? Anyway, whatever they did, did not fix it. But
again, that was last year. This year 2010 the other 1/2 has been playing
with it and entering a few jobs and ....seems to be working again.

The last 2009 job number was 091010 and that's where it seemed to go
weird.... but 2008 had more jobs and nil issues...

I don't trust it enough to sit there and enter all the jobs that have
not been yet put in

Any assistance appreciated

Softy

 

[Gina Whipp]

Softy,

From your description it sounds like the database needs to be *reviewed* by
someone familiar with Access so the code can be reviewed and an assessment
of what needs to be done can be documented. Unless you are willing to
*learn* (and we volunteers will guide you along for FREE) then try checking
your local universities or colleges...

--
Gina Whipp
2010 Microsoft MVP (Access)

"I feel I have been denied critical, need to know, information!" - Tremors
II

http://www.regina-whipp.com/index_files/TipList.htm

Sorry for the "vague" original question but I am that way about this and
what its doing...and also, I was not sure if I were in the right NG

First, the DB belongs to the other 1/2 and I have never really used it.
Just looked at what she told me and tried a few things. My knowledge of
MS Access is very limited.

As best I can....
The database seemed to have run out of job numbers for 2009. All job
numbers start with the year prefix i.e 08xxx or 09xxx.
We gave up using it around August 09 as new jobs entered were gone next
day...and when logging in, a message popped up saying

QUOTE
"The job ID is not using the current year as count prefix, do you wish
to update it to the current year"

If we change the date of the computer to 2009.... and start the database
so the DB thinks its 2009... the same above error pops up. Closing and
changing back to 2010, the error is gone.

How here today, gone tomorrow was happening I have no idea

Now playing with it in 2010, it seems to be working again but obviously
not fixed

We did take it down to the local computer shop. He said he fixed it by
"adding more numbers"?? Anyway, whatever they did, did not fix it. But
again, that was last year. This year 2010 the other 1/2 has been playing
with it and entering a few jobs and ....seems to be working again.

The last 2009 job number was 091010 and that's where it seemed to go
weird.... but 2008 had more jobs and nil issues...

I don't trust it enough to sit there and enter all the jobs that have
not been yet put in

Any assistance appreciated

Softy

 

[John W. Vinson]

The database seemed to have run out of job numbers for 2009. All job
numbers start with the year prefix i.e 08xxx or 09xxx.
We gave up using it around August 09 as new jobs entered were gone next
day...and when logging in, a message popped up saying

QUOTE
"The job ID is not using the current year as count prefix, do you wish
to update it to the current year"

This is not a message from the Access program itself, but from some very
specific code that your contractor wrote to assign new job numbers.

If this is the only critical problem that you're having, and if you're
willing, I could take a look and see what's giving the error. You could send
me the database by:

0. MAKE A BACKUP!!!! <you should routinely have the database backed up but
it's particularly important when you'll be doing something drastic like
Compact)
1. Opening it while holding down the SHIFT key to bypass any startup code
2. Selecting Tools... Database Utilities... Compact and Repair Database from
the menu
3. Exit Access, and in Windows Explorer, right click the .mdb file and choose
Send To... Compressed (zipped) Folder; or if you have WinZIP or a similar
utility, use it to create a zipped file
4. Email the file to me at jvinson <at> wysard of info <dot> com (edit out the
blanks and edit in the punctuation)

I can't guarantee when or if I can get it fixed but I'll be glad to take a
look at it, free of charge.

 

[dasadler via AccessMonster.com]

Softy,

I would be happy to take a look also. I am not an Access or VBA wizard but I
have created a database with a similar (I expect) numbering scheme for my
jobs. If you want to zip it and send it then I will take a look free of
charge. I only ask that if you get it fixed through this forum that the
actual problem and solution be written up so that others might benefit.

Dan

 

[Gina Whipp]

John,

Thanks, I would have extended the offer but I have to folks from the
newsgroup who I am helping for free already!

--
Gina Whipp
2010 Microsoft MVP (Access)

"I feel I have been denied critical, need to know, information!" - Tremors
II

http://www.regina-whipp.com/index_files/TipList.htm

The database seemed to have run out of job numbers for 2009. All job
numbers start with the year prefix i.e 08xxx or 09xxx.
We gave up using it around August 09 as new jobs entered were gone next
day...and when logging in, a message popped up saying

QUOTE
"The job ID is not using the current year as count prefix, do you wish
to update it to the current year"

This is not a message from the Access program itself, but from some very
specific code that your contractor wrote to assign new job numbers.

If this is the only critical problem that you're having, and if you're
willing, I could take a look and see what's giving the error. You could send
me the database by:

0. MAKE A BACKUP!!!! <you should routinely have the database backed up but
it's particularly important when you'll be doing something drastic like
Compact)
1. Opening it while holding down the SHIFT key to bypass any startup code
2. Selecting Tools... Database Utilities... Compact and Repair Database from
the menu
3. Exit Access, and in Windows Explorer, right click the .mdb file and
choose
Send To... Compressed (zipped) Folder; or if you have WinZIP or a similar
utility, use it to create a zipped file
4. Email the file to me at jvinson <at> wysard of info <dot> com (edit out
the
blanks and edit in the punctuation)

I can't guarantee when or if I can get it fixed but I'll be glad to take a
look at it, free of charge.

 

[dasadler via AccessMonster.com]

Oops - my name is Don... not Dan

Softy,

I would be happy to take a look also. I am not an Access or VBA wizard but I
have created a database with a similar (I expect) numbering scheme for my
jobs. If you want to zip it and send it then I will take a look free of
charge. I only ask that if you get it fixed through this forum that the
actual problem and solution be written up so that others might benefit.

Dan

Guy's and Gal's

[quoted text clipped - 6 lines]

Softy

 

[softy]

Thanks for the offer... will do BUT how do I decipher your email address

Jeff

Thanks

SoftY

 

[dasadler via AccessMonster.com]

softy - not sure if your reply was directed to me but I couldn't find a Jeff
so I'm taking a chance. You can email me at dasadler<at>gmail<dot>com
Regards, Don

Thanks for the offer... will do BUT how do I decipher your email address

Jeff

Thanks

SoftY

Softy,

[quoted text clipped - 16 lines]

 

[John W. Vinson]

Guy's and Gal's

I have a database that is based on MS access that I am having trouble
with. I actually paid someone to create this for me but they refuse help
as they have gone out of business! (wonder why-)

First, before I show that I am a complete idiot and describe the fault,
** am I in the right group for that type of help ** ??

Softy

I got your email, Softy, but what you sent me was a .mde file - which has all
the VBA source code stripped out and cannot be debugged or repaired. Did your
contractor leave you a .mdb file as well? That's what will be needed to find
and fix it.

If they didn't give you a .mdb and aren't available to fix it, you've been
ripped off, I fear!