Quick question

  • Thread starter Thread starter Joe Cilinceon
  • Start date Start date
J

Joe Cilinceon

I have a program written using Office XP Developers package that I wrote
about 4 years ago. I've been running the program on 2 different machines now
since then without a single problem. Due to one machine being taken out by
lightning I was forced to replace it with a new system from Dell that I
could find XP still available for as a choice of OS.

At any rate I got Office XP Developer to install with a bit of effort but
now have it up and working. My Access program is a stand a lone but very
complicated. At any rate the program is now dropping data between forms and
sub forms on the new machine while still working fine on the old system.

When I wrote this years ago I used a couple of lines of code that would
show me with a popup screen what was happening with things like SQL formats
as well as variable contents. For the live of me I can't remember now how I
did it. Any help on this would be greatly appreacieted as I really need to
solve the problem on the new machine.

Oh and one other not both the old machines are running different versions of
XP. The one being replaces ran XP Home, the other old machine is running XP
Media Center with both having 2G ram. The new machine also a Dell I got with
4G ram installed but running XP Pro. All 3 machines had all patches,
upgrades etc installed current.

Thanks again for in input..

Joe Cilinceon
 
You probably need to make sure that the new machine has all the Office XP
Service Packs installed.
 
Arvin said:
You probably need to make sure that the new machine has all the
Office XP Service Packs installed.

All the latest service packs installed at this point. I don't want to use
break points as that is a bit too combersome for an intermettin problem
like this. I used this method to narrow down what is happening with
variables and the method I used allowed me to close the program at that
point without going any further.

I seemed to think is was something like MsgBox command but too 3 lines of
simple code. The reason this would come in handy as it happens sometimes the
first time I go to enter a payment or may not till the 20th payment I enter.
No rhyme or reason to when it happens. Again it only happens on the new
machine not the older 2 machines.
 
I figured out what I was looking for so thanks anyhow.

What I wanted was to add this to my code before any DoCmd took place.

MsgBox SQL
Exit Sub
 
Joe said:
I figured out what I was looking for so thanks anyhow.

What I wanted was to add this to my code before any DoCmd took place.

MsgBox SQL
Exit Sub

Actually that should read as follows:
MsgBox strSQL
Exit Sub
 
Back
Top