Bugs when using Access 200 DB on Access 2003?

[redpelon]

I have developed a database in Access 2000, and it works wonderfully
on all the computers I've tested it on... however, when I have tested
it on two computers with Access 2003 (haven't tested it on more 2003
computers yet), it gets a little buggy and I need to fix that before I
distribute this program, because it will go to about 300 clients, and
I need to have bugs hammered out before I distribute it.

the two bugs I know of right now are this:

For example, on one of the main windows (form), you get a list of the
records, in a continuous form. On all the versions I've tested,
except for 2003, I have a simple macro set up so when you double click
on the record, it takes you to the full record where you can edit the
information.. the main window is just a summary. It is set to load up
the full record by the autonumber ID.. it works great with no
problems on the other versions, yet on 2003 when i click on that, it
just takes me to a blank record, not the correct one... is this
something with 2003?

I have 2 other similar forms that when you double click on the record
summar, you are taken to the full record with similar macros.. again
that works on all version so far except 2003..

The other bug is that on that same main form, I have a dlookup funcion
running - in simple terms, if the dlookup finds what im looking for,
it just prints "yes". On the main form, it is just blank in the box
where i wrote the dlookup code (on the access 2003 machines.. it works
beautifully on other version). However, I have the exact same code on
the full record form, and it works fine on the 2003 versions... i
can't understand why with the same code on both forms why it would
work on one and not the other?

Any ideas?

 

[missinglinq via AccessMonster.com]

They'll be others here that can give you more in depth info on Access 2003,
but I believe that Macros present a problem unless security is set just so;
set to Low, perhaps!

--
There's ALWAYS more than one way to skin a cat!

Answers/posts based on Access 2000

Message posted via AccessMonster.com

 

[redpelon]

I have developed a database in Access 2000, and it works wonderfully
on all the computers I've tested it on... however, when I have tested
it on two computers with Access 2003 (haven't tested it on more 2003
computers yet), it gets a little buggy and I need to fix that before I
distribute this program, because it will go to about 300 clients, and
I need to have bugs hammered out before I distribute it.

the two bugs I know of right now are this:

For example, on one of the main windows (form), you get a list of the
records, in a continuous form. On all the versions I've tested,
except for 2003, I have a simple macro set up so when you double click
on the record, it takes you to the full record where you can edit the
information.. the main window is just a summary. It is set to load up
the full record by the autonumber ID.. it works great with no
problems on the other versions, yet on 2003 when i click on that, it
just takes me to a blank record, not the correct one... is this
something with 2003?

I have 2 other similar forms that when you double click on the record
summar, you are taken to the full record with similar macros.. again
that works on all version so far except 2003..

The other bug is that on that same main form, I have a dlookup funcion
running - in simple terms, if the dlookup finds what im looking for,
it just prints "yes". On the main form, it is just blank in the box
where i wrote the dlookup code (on the access 2003 machines.. it works
beautifully on other version). However, I have the exact same code on
the full record form, and it works fine on the 2003 versions... i
can't understand why with the same code on both forms why it would
work on one and not the other?

Any ideas?

Just something i read, could this be the issue?

Is it the way that access 2003 refers to subforms as controls, meaning
i should create a special "access 2003" version of the program, to
include the .Form. in the macro calls, and in my dlookup funcion?

thanks

 

[redpelon]

They'll be others here that can give you more in depth info on Access 2003,
but I believe that Macros present a problem unless security is set just so;
set to Low, perhaps!

--
There's ALWAYS more than one way to skin a cat!

Answers/posts based on Access 2000

Message posted via AccessMonster.comhttp://www.accessmonster.com/Uwe/Forums.aspx/access-forms/200707/1

I appreciate that... is that something I would have to do only on
access 2003, or is it something i can set on 2000 and have it set for
when the user runs it through 2003? I wont be able to personally
install this program on all hte 300 machines.

Thanks for the quick response.

 

[Redpelon]

Just something i read, could this be the issue?

Is it the way that access 2003 refers to subforms as controls, meaning
i should create a special "access 2003" version of the program, to
include the .Form. in the macro calls, and in my dlookup funcion?

thanks- Hide quoted text -

- Show quoted text -

Also a little more detail - where im getting these errors on the
dlookup and the macros i am calling them from a subform..

so i went in and changed the references to the subform and
added .Form. before the subform name, and it still works on my access
2000, so thats a good sign, and i'll test it on my wife's computer
tonight which has 2003... hoping maybe that helped?

i tend to send a few too many messages, dont I .

 

[missinglinq via AccessMonster.com]

Sorry, but these settings were not available in ACC2000. They have to be set,
I think, for each PC running Access 2003.

--
There's ALWAYS more than one way to skin a cat!

Answers/posts based on Access 2000

Message posted via AccessMonster.com

 

[Redpelon]

Also a little more detail - where im getting these errors on the
dlookup and the macros i am calling them from a subform..

so i went in and changed the references to the subform and
added .Form. before the subform name, and it still works on my access
2000, so thats a good sign, and i'll test it on my wife's computer
tonight which has 2003... hoping maybe that helped?

i tend to send a few too many messages, dont I .

Okay I tested the database on a computer with Access 2003, with the
changes in the references to the subforms by using Form! and it still
didn't work.... neither the Dlookup nor the macros..

It's so annoying, any other tips on why the Dlookup in the subform of
the main form shows up blank while the same dlookup on another form
(not in a subform) works fine? And why the macros that call up the
detail form from the main form only show up blank?